chore: rename silver references to OpenGovMail - #293
Merged
maneesha-xyz merged 1 commit intoAug 12, 2026
Conversation
Renames the remaining legacy "silver" naming: the CONTRIBUTING heading, the auth test fixtures (silver.example.com, silver OU handle, silveruser type), and the Silver Bot CI secrets, variables and branch prefix. Closes OpenGovMail#292
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
2 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.
Description
Renames the remaining 35 legacy
silver/Silver/SILVERreferences toopengovmail/OpenGovMail/OPENGOVMAILacross 6 files.Docs
docs/CONTRIBUTING.md—Raven (Silver Go IMAP)→Raven (OpenGovMail Go IMAP)in the heading and introAuth test fixtures
internal/server/auth/authenticate_oauth_test.go,helpers_internal_test.go,authenticateuser_test.go— fixture domainsilver.example.com→opengovmail.example.com, OU handlesilver→opengovmail, user typesilveruser→opengovmailuserCI workflows
.github/workflows/update-security-policy.yaml—secrets.SILVER_BOT_TOKEN→secrets.OPENGOVMAIL_BOT_TOKEN,vars.SILVER_BOT_NAME/EMAIL→vars.OPENGOVMAIL_BOT_NAME/EMAIL, branch prefixsilver-bot/→opengovmail-bot/, and the "Silver Bot" step names and PR body text.github/workflows/welcome-outside-contributors.yaml—secrets.SILVER_BOT_TOKEN→secrets.OPENGOVMAIL_BOT_TOKENCloses #292
Type of change
How to test
go test ./internal/server/auth/...— passes locally (ok raven/internal/server/auth 12.160s). Several of these tests assert on the exact fixture strings, so a partial rename would have failed the run.This PR renames CI secret and variable references. Those names are bound to entries in the org/repo settings, not to anything in this repo. Before merging, confirm all three exist under
OpenGovMailwith the same values and permissions as the currentSILVER_BOT_*entries:OPENGOVMAIL_BOT_TOKEN(secret)OPENGOVMAIL_BOT_NAME(variable)OPENGOVMAIL_BOT_EMAIL(variable)If they are missing, GitHub resolves them to an empty string rather than failing the run, so the breakage is silent:
update-security-policy.yamlwould check out and open its release PR with an empty token — the automated security-policy job breaks on the next release.welcome-outside-contributors.yamlhas a|| github.tokenfallback, so it would quietly stop commenting as the bot and use the default token instead.Once a release cycle confirms both workflows still pass, the old
SILVER_BOT_*secret and variables can be deleted.Notes for reviewers
docs/CONTRIBUTING.mdon different lines (this PR line 1–3, chore: rename LSFLK references to OpenGovMail after org transfer #291 line 28), so they will not conflict.