Deliberately broken PR to demonstrate that the M0.2 CI gates reject bad PRs.
This PR contains:
A commit subject that violates Conventional Commits — commitlint must reject it.
A fake AWS access key string — gitleaks must reject it.
Expected outcome: CI fails, status check shared does not turn green, branch protection refuses the merge. Do not merge. Close after CI fails.
Linked milestone: M0.2
Why
M0.2 acceptance criterion: "a deliberately-broken PR is rejected by every check."
How
Trivial — one markdown file with a regex-bait secret. Both bad-commit-subject and bad-content baked in.
Test plan
This PR IS the test. CI must fail. Close after observing.
Risk
Zero — branch protection blocks merge even if reviewer slips.
Checklist
n/a — demo PR, not production-bound.
## What
Deliberately broken PR to demonstrate that the M0.2 CI gates reject bad PRs.
This PR contains:
1. A commit subject that violates Conventional Commits — `commitlint` must reject it.
2. A fake AWS access key string — `gitleaks` must reject it.
Expected outcome: CI **fails**, status check `shared` does not turn green, branch protection refuses the merge. **Do not merge.** Close after CI fails.
Linked milestone: **M0.2**
## Why
M0.2 acceptance criterion: "a deliberately-broken PR is rejected by every check."
## How
Trivial — one markdown file with a regex-bait secret. Both bad-commit-subject and bad-content baked in.
## Test plan
This PR IS the test. CI must fail. Close after observing.
## Risk
Zero — branch protection blocks merge even if reviewer slips.
## Checklist
n/a — demo PR, not production-bound.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Deliberately broken PR to demonstrate that the M0.2 CI gates reject bad PRs.
This PR contains:
commitlintmust reject it.gitleaksmust reject it.Expected outcome: CI fails, status check
shareddoes not turn green, branch protection refuses the merge. Do not merge. Close after CI fails.Linked milestone: M0.2
Why
M0.2 acceptance criterion: "a deliberately-broken PR is rejected by every check."
How
Trivial — one markdown file with a regex-bait secret. Both bad-commit-subject and bad-content baked in.
Test plan
This PR IS the test. CI must fail. Close after observing.
Risk
Zero — branch protection blocks merge even if reviewer slips.
Checklist
n/a — demo PR, not production-bound.
Pull request closed