Skip to main content
Every merge to master in the Termux Monorepo must pass two mandatory CI gates. This page explains what each gate checks, how to run them locally, and the ArchWiz-Gate concept that ties them together.

Mandatory gates

Run both scripts from the monorepo root before opening or merging any PR:
Both must exit with code 0. If either fails, the merge is blocked.

ArchWiz-Gate concept

The ArchWiz-Gate, documented in docs/ARCHW1Z-GATE.md, is the umbrella framework that enforces these two gates. It defines the contract between the monorepo and the CI system: no commit reaches master unless both gates are green.

Sentinel 5-gate verification

ArchWiz includes a deeper verification layer in archwiz/sentinel.py. Sentinel runs five internal gates before a change is considered safe to promote: Run Sentinel manually with:
Both repo_gate.py and termux_smoke.py must pass with exit code 0 before any merge to master. Do not bypass or skip either gate, even for urgent fixes. If a gate fails, fix the root cause and rerun.

Running gates in CI

For GitHub Actions or other CI systems, add both scripts as sequential steps:
If either step fails, the workflow should stop and the PR must not merge.

Next steps