The change-request check and the no-requirement label
Every pull or merge request cites existing, non-retired record codes; trivial changes carry a label instead.
For: Team developer, Project lead
What it checks
- Fails without any record code, with an unknown code, or with a Retired record. A story code alone links the work but does not pass.
- Warns on Draft or Approved records.
- Skips change requests labelled
no-requirement.
The file check
- A second job sends the files the change request changes; CorPole needs no GitHub or GitLab credentials for this.
- Fails when ungoverned code is changed under the enforced onboarding gate; warns under the advisory one.
- Warns about a module whose findings are still under review, files outside the modules of the cited work, other open change requests changing the same files, and a change request during an emergency that does not cite the emergency defect.
Set it up
Run /corpole:init (it detects GitHub or GitLab) and add CORPOLE_TOKEN with a service token: a repository secret on GitHub, a masked CI/CD variable on GitLab (with the include: of .gitlab/corpole.yml).