Repository navigation
Board: UCLA events editor sign-in - #102
Merged
Merged
Conversation
- BOARD_UCLA_EVENTS_PASSWORD signs in to /board/ucla as the events
editor (the socials role Berkeley already has): the member view plus
adding, editing and deleting events. Event writes accept only that
chapter's admin or events-editor session; everything else stays
admin-only, and admins-only content stays hidden.
- The header says "Signed in as events editor".
- The change log labels each entry by the role that made it ("UCLA
events editor", "UCLA admin"). The optional "Your name" box also shows
on the events tab for the events editor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzNDQSmhjgKE63rwUnwcMq
# Conflicts: # lib/board/chapters.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Adds an events editor sign-in for UCLA, the same as Berkeley's socials editor password.
BOARD_UCLA_EVENTS_PASSWORD. It's listed blank in.env.example; the value isn't in the code./board/uclawith it gives the member view, plus adding, editing and deleting events (dates, times, locations, leads, status). Nothing else is editable, and admins-only content stays hidden (admins-only announcements, unassigned tasks, the Changes tab, email results).This reuses the existing
socialsrole, which UCLA's hub now calls the events editor.Tested (local production build)
Deploy
Add
BOARD_UCLA_EVENTS_PASSWORDin Railway with a value different from the other passwords, and give it to whoever runs UCLA's events.Generated by Claude Code