Skip to content

Received 2 invites for an "Event" #2861

Closed

Description

@KimberleyCook

Description of the issue 📄

I received two email invites for the Prompt Your Portfolio with Google AI Studio Event. It should just be one. And it should be the second one that isn't mentioning a coach.

The logic should be that is invites are sent to both students and coaches it shouldn't specify that a coach is needed. It should just be a general invite. I hope this makes sense! Drop me a message if more information is needed.

Screenshots 📷

Image

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

Activity

  1. mroderick commented on Sep 9, 2026

    @mroderick
    Collaborator

    Hi Kimberley! We found the cause.

    Members can be subscribed to a chapter as both a student and a coach — that's common. When event invitations go out, students and coaches are invited in two separate passes, and each pass only skips people who already have an invite of the same type. So anyone on both lists gets two emails: one student invite, one coach invite. The same happens for workshops.

    The "Coach Invitation" wording is a second small bug: for events with no audience set, coach emails should say a general "Invitation", but the check doesn't treat "no audience" correctly.

    Proposed fix: skip anyone who already has an invite to the event or workshop, whatever its type — one email per person. And label coach emails as "Coach Invitation" only when the event is actually for coaches.

    This affected 387 members on the Prompt Your Portfolio event, so it's not just you — thanks for reporting!

    Happy with that approach?

  2. KimberleyCook commented on Sep 11, 2026

    @KimberleyCook
    ContributorAuthor

    @mroderick yeah perfect thank you!

  3. added a commit that references this issue on Sep 28, 2026
    26d9499
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions