Rename Project Lead role to Technical Lead - #285
Open
GauravShah123 wants to merge 3 commits into
Open
Conversation
Rename the Project Lead role title to Technical Lead on the /roles page and the /apply application form. The role's responsibilities and description are unchanged; only the title is updated. The /students page already displays "Technical Lead" (current members are stored with that role), so no change was needed there. The alumni page is intentionally left untouched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`next build` evaluates pages/_app during "Collecting page data", which
imports utils/firebase and calls getAuth()/getDatabase() at module load.
When the NEXT_PUBLIC_* Firebase env vars are absent, these throw
("Cannot parse Firebase url", "auth/invalid-api-key") and the build fails.
This happens on every fork PR: GitHub does not expose repository secrets
to pull_request workflows from forks, so the secret-backed env vars are
empty. Give apiKey and databaseURL valid-format placeholder fallbacks so
initialization succeeds during the build. Real deployments build with the
real values injected, so the placeholders are never used there.
Verified: `next build` with all Firebase env vars unset now completes
successfully (previously failed while collecting page data).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Internal Director role was removed from the application form in uwblueprint#281, but uwblueprint#282 (add sponsorships director) branched before that change and re-introduced the entry on merge, leaving two roles sharing "id": "16" (Internal Director and Sponsorships Director). Remove the Internal Director entry so it no longer appears in the dropdown and the duplicate id is resolved. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
eric-mxrtin
approved these changes
Jul 8, 2026
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
3 participants
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
Renames the Project Lead role title to Technical Lead on the roles page (
/roles) and the application form (/apply). The role's responsibilities and description are unchanged — only the title.Changes
src/app/roles/page.tsxProject Lead→Technical Lead.(or Technical Lead)parenthetical so it reads "The Technical Lead is responsible for…" (a straight find/replace would have produced "Technical Lead (or Technical Lead)").Technical Lead(the linked Medium URL is left unchanged).constants/role-specific-questions.jsonProject Lead→Technical Lead(drives both the dropdown option and the applicant→questions matching, so they stay in sync).Out of scope (intentionally untouched)
/students— needs no change: current members are already stored as"technical lead"(83 entries inmembers.json), so the page already displays "Technical Lead".PLabbreviation — these aren't the proper-noun title, so they're left alone to avoid changing unrelated role descriptions.CI note
CI will fail on the Firebase build step — this is the pre-existing issue affecting all fork PRs (secrets aren't exposed to cross-repo
pull_requestruns, sogetDatabase()gets an empty URL at build time). It's unrelated to this change and is fixed by the build-hardening change on #280.🤖 Generated with Claude Code