CalvinBackup/OBLITERATUS
1
0
Fork 0
mirror of https://github.com/elder-plinius/OBLITERATUS.git synced 2026-08-30 06:30:37 +02:00
Code Issues Packages Projects Releases Wiki Activity

ci: adopt tiered contributor validation

Browse Source
This commit is contained in:
Joseph Magly
2026-08-20 23:11:24 -04:00
parent 0d4d439f22
commit 38efd3dc0a
37 changed files with 916 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/pull_request_template.md
+7 -10
View File
@@ -22,19 +22,16 @@ Exact head SHA: `TBD`
| Negative and boundary tests | TBD | |
| `python -m ruff check --select F app.py obliteratus tests scripts` | TBD | |
| `uv lock --check` | TBD | |
| `python -m pytest` | TBD | |
| `python -m build --sdist --wheel` | TBD | |
| Selected PR core/risk tests | TBD | |
| Package build, when package inputs changed | not applicable / TBD | |
| Import and CLI smoke checks | TBD | |
| Applicable risk-surface checks | TBD | |
| Conditional hardware/service gates | not applicable / TBD | |
Coverage or mutation impact:
- Repository line/branch:
- Changed-line:
- Touched-module regression:
- Mature CPU scope:
- Mutation score, when applicable:
- Additional maintainer coverage or release-depth work needed:
## Research or performance evidence
@@ -46,7 +43,7 @@ Use `Not applicable` when this pull request makes no research or performance cla
## Checklist
- [ ] I added or updated tests for every changed behavior.
- [ ] I added or updated focused tests for changed behavior, or identified where maintainer help is needed.
- [ ] I covered relevant failure, boundary, and malformed-input paths.
- [ ] The default test path remains deterministic, offline, credential-free, and CPU-safe.
- [ ] I updated `ci/test-risk-map.json` or conditional policy when ownership changed.
@@ -58,6 +55,6 @@ Use `Not applicable` when this pull request makes no research or performance cla
- [ ] Every commit has a verifiable signature from its actual author or approved integration identity.
- [ ] The branch has not been force-pushed and the exact head is ready for review.
New changes are expected to include their complete relevant test suite. The one-time
maintainer courtesy for already-reviewed legacy pull requests does not apply to new
submissions.
A green PR gate makes the submission reviewable. Maintainers may add further tests
or hardening in separately attributable commits before merge; behavior changes with
zero relevant coverage remain blocked.