Skip to content

docs: record that master is PR-protected in AGENTS.md #2386

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

Open
just-jeb wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: record that master is PR-protected in AGENTS.md #2386

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
2 changes: 2 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,8 @@ Lerna-Lite manages versioning and publishing. Packages use **independent version

**MUST:** When creating a pull request, read `.github/PULL_REQUEST_TEMPLATE.md` and use its structure for the PR body. Fill in all sections: PR checklist, PR type, current behavior, new behavior, and breaking change flag.

**MUST NEVER:** Push straight to `master`. A repository ruleset requires every change to arrive through a pull request and to pass the `ci-pass` status check. Jeb is a bypass actor, so a direct push **succeeds** and only reports the bypass in its output — the guard will not stop you, which is exactly why this is written down. This applies to documentation-only commits too. Note that `gh api repos/just-jeb/angular-builders/rules/branches/master` returns `[]` for a bypass actor, so an empty rules list is not evidence that master is unprotected.

## Local Failure Triage

A failing local jest or build run here is **frequently environment contamination, not a
Expand Down
Loading