Release v1.36.0 — Rulings that block a merge · MikeHeid/overture

A broken ruling can now fail a pull request, with no console server.

plugin/kit/rulecheck.py checks the committed ruling files (fold.py export, .overture/locked by default) against the checkout. It needs no store, server or network. It exits 0 when every ruling holds, 1 when one is broken and 2 when it could not run.
--base REF reads the rulings, and .overture.json, as committed at the pull request's base, so a pull request cannot pass by editing or deleting a ruling file. A re-lock or settle inside the pull request is listed as re-ruled for the reviewer.
GitHub Action:
```
- uses: actions/checkout@v4
  with: {fetch-depth: 0}
- uses: MikeHeid/overture@v1.36.0
```
It writes a job summary, and when a ruling breaks or a reviewer needs to look, it keeps one comment on the pull request up to date. Text from ruling files cannot render as markup, HTML, links or @mentions in that comment.

See CHANGELOG.md "Rulings that block a merge (1.36.0)" and the README section "Block a merge that breaks a ruling".

Zip sha256: 584601f780837b9f04190cf2ec8608d90338fce4b68aef8427d67fd32ad358f3

Navigation Menu