Skip to content

Fix organizer username in participation request emails - #2511

Open
pttydou wants to merge 1 commit into
codalab:developfrom
pttydou:fix/2445-user-applied-email
Open

Fix organizer username in participation request emails#2511
pttydou wants to merge 1 commit into
codalab:developfrom
pttydou:fix/2445-user-applied-email

Conversation

@pttydou

@pttydou pttydou commented Aug 23, 2026

Copy link
Copy Markdown

A brief description of the purpose of the changes contained in this PR.

Participation request emails reused the participant context for organizer recipients, so the base template greeted organizers with the participant username. This sends an individual notification to each active organizer with their own user context while leaving the participant receipt unchanged.

Issues this PR resolves

Fixes #2445

A checklist for hand testing

  • Apply to a non-auto-approved competition and verify each active organizer is greeted with their own username.
  • Verify the participant still receives the application confirmation and deleted organizers receive no email.

Any relevant files for testing

  • src/apps/competitions/tests/test_emails.py

Tests:

  • .venv\Scripts\python.exe -m pytest src/apps/competitions/tests/test_emails.py -q with DOMAIN_NAME=localhost and DJANGO_SETTINGS_MODULE=settings.test (1 passed)
  • .venv\Scripts\python.exe -m flake8 src/ (passed)

The full Docker/PostgreSQL suite was not run locally because Docker is unavailable on this Windows host; CircleCI covers that suite.

Checklist

  • Code review by me
  • Hand tested by me
  • I'm proud of my work
  • Code review by reviewer
  • Hand tested by reviewer
  • CircleCi tests are passing
  • Ready to merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Username problem in email "User applied to your competition"

1 participant