Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Dual Invitiation issue

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

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

@mroderick y travaille déjà.

Depuis le 15/10/2026.

  • #3042 par @mroderick — ouverte

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
42/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
ruby
Domaine
backend

Piste de recherche

The payload names no files. Start with the event invite logic that decides whether an invite is sent or marked as skipped, and look for a check that stops a second invite once a user already has one for the same event. Reproduce with a test user who is both a student and a coach for one event, then confirm both invite emails are sent. Done means the coach invite is no longer skipped and the user receives both.

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

Description

Description of the issue 📄

If a user on the site is signed up as a student and a coach they are currently only receiving one invite email to rsvp.

Example will be for user 12102

They messaged reporting they have received a student invite but not a coach invite for the event on 27th October in Brighton. I have checked the event invite log and can see the coach invites are showing as skipped.

This means the user can RSVP as a student only and not a coach.

Screenshots 📷

Screenshots would show personal info of the invite logs

Steps to fix 🛠

To do 📋

  • Claim this issue (comment below, or assign yourself if you are part of the codebar org)
  • Fork and clone the repository
  • Update the relevant files. Follow the steps to fix section in this issue.
  • Commit your changes as one commit. Use the title of this issue as your commit message
  • Submit a pull request
  • Mention this issue in the PR description by including it's number
  • Have your pull request reviewed & merged by a codebar team member
Langage dominant
Ruby
Étoiles
106
Forks
208
Merge moyen
19 h 31 min
PR mergées (30 j)
84

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 codebar/planner

Toutes les issues de codebar/planner

Issues similaires

Plus d'issues Ruby

Recevez les nouvelles issues par e-mail

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