Repository navigation
docs(governance): only one person could administer Parsec - #120
Merged
Merged
Conversation
foothillsdigital is now an admin of the repository as well, so either maintainer can change settings, rulesets and access, and keep Parsec going if the other can't.
jamesconwaydev
enabled auto-merge (squash)
November 19, 2026 23:57
foothillsdigital
approved these changes
Nov 20, 2026
foothillsdigital
left a comment
Collaborator
There was a problem hiding this comment.
Checked fa7e055. gh api repos/parsec-html/parsec/collaborators lists both of us as admin, so the sentence is true as it stands. It fits with the lines around it: release tags still need an admin and a key in allowed_signers, and both of us have both. Approving.
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.
Problem
Only James had admin rights on the repository, so if he became unavailable, nobody could change its settings, rulesets or access. OpenSSF's
access_continuitycriterion, at silver and gold, asks for exactly that continuity.Change
@foothillsdigital is now an admin of
parsec-html/parsec, and GOVERNANCE.md says so: either maintainer can change settings, rulesets and access, and keep Parsec going if the other can't. Release tags still need an admin and a key in.github/allowed_signers, which both maintainers have.Tests
gh api repos/parsec-html/parsec/collaboratorslists both maintainers with theadminrole.