Contributor title: an account made from a member's invite key can take the member's title

Ouverte
#3,687 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
Une demi-journée
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go

Piste de recherche

Start with the operations sync that writes contributors.json and fills members[].accounts, then trace how /contributor here builds the member's group from that file — the contributor.go header comment describes the invite-key link you need to exclude. Compare that group-construction path against the OAuth sign-in records so you can tell an invite-linked account from a member-linked one. Done means the group only includes OAuth-linked accounts, plus a test asserting an invite-linked account gets ErrNotInGroup and a 404 from the website path.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area: server bug priority: medium

The Contributor title (#3358, owner 2026-11-14 #3488) sits on one account per member, which the member can move "to another of their own". A member's group (contributors.json members[].accounts, written by the operations sync) holds every account linked to the member's Discord id. That includes accounts created from the member's invite keys (contributor.go header: "invite keys link any number of accounts to one Discord id").

An invite-made link is the key giver's Discord, not the player's (opensro-web#105, the account overview treats it as none). So a friend who signed up with the member's key is in the member's group, and can move the yellow title onto their own account: /contributor here in chat today, and the website's Carry it here once #3660 and web#154 land.

Fix

The group should hold only accounts linked by the member's own Discord sign-in (OAuth), not those linked through an invite key. That is the operations sync's input, plus a test that an invite-linked account gets ErrNotInGroup and answers 404 on the website.

Langage dominant
Go
Étoiles
97
Forks
61
Merge moyen
4 h 14 min
PR mergées (30 j)
913

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de opensro-dev/opensro

Toutes les issues de opensro-dev/opensro

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.