Skip to content

docs(specs): record course-materials-ng's bypass for its maintainer #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StoneyJackson merged 1 commit into from
Oct 13, 2026
Merged

docs(specs): record course-materials-ng's bypass for its maintainer #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion dev-docs/specs/2026-10-13-devcontainer-permissions-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,12 @@ Set by an org owner, before any container gets push access.
Per repo: org rulesets need GitHub Team, which ourPLCC does not have.
"Apply the rulesets" is therefore a step in creating any ourPLCC repo. The
release Apps are the only bypass actors; nobody else bypasses, org owners
included.
included, with one exception: course-materials-ng's `main` also lets its
maintainer Alain Kägi (`alainkaegi`) bypass, because he maintains it by
pushing to `main` directly. Its `main` still needs the ruleset for everyone
else: `deploy.yml` runs on every push to `main` with the release App's token,
which reaches every repo in the App's installation. The remaining risk is
that one contributor's token.

- **`main`**, every repo except `change-requests` (`dev` included): require a
pull request, block force-pushes, block deletion.
Expand Down
Loading