Skip to content

ci probe: path gating on a fork - #5

Closed
Manuthor wants to merge 14 commits into
ci-probe-basefrom
ci-probe-head
Closed

Manuthor wants to merge 14 commits into
ci-probe-basefrom
ci-probe-head

Conversation

@Manuthor

Copy link
Copy Markdown
Owner

Fork run: no upstream secrets.

- Add .github/ci-paths.toml: per-unit path regexes, full/ignore lists, fail-safe on unmatched files.
- Add mise task dev:ci-changes (ci_changes.py) classifying a PR diff into skipped units.
- Add the `changes` job to main.yml and pass skip-units through test_all, test-db, test-interop, test-group and test_windows.
- ci-paths.toml: drop server_core from ui, interop:*, pki, pkcs11, obs, hsm, db:*, cloud and the Windows mirrors; add db_core and kmip_wire sets and feature-owned paths
- ci_changes.py: update self_test for the narrower gating
- CHANGELOG: describe the narrower PR gating
- ci-paths.toml: drop workflow, ci-paths.toml and ci_changes.py from `full`; each reusable workflow triggers its direct units plus one representative leg
- ci_changes.py: self-test a workflow-only change set (9 units instead of 37)
- test_ci_changes.py: 43 scenarios (docs, ui, rust core, db backends, feature crates, workflows, fail-safes) on the real ci-paths.toml
- dev:ci-changes --self-test also runs them, so the `changes` job gates on them
- test_ci_changes.py: one triggering sample per unit (asserts full unit coverage and that no sample hits full)
- test_ci_changes.py: classify()/load_config() on an inline TOML (empty diff, full, orphan, ignore, lookahead, invalid config)
- ci_changes.py: drop self_test(), now fully covered by the unit tests; --self-test only runs them via the task
- ci-paths.toml: db:sqlite triggers only on its task script and the workspace set, not on workflow files
- test-db.yml and test-group.yml are ignored wrappers; main.yml and test_all.yml keep their direct units
- test_ci_changes.py: workflow-only set is 8 units; wrappers alone run nothing
- ci-paths.toml: drop main.yml, no-nix.yml and test_windows.yml from the no-nix and windows-cargo-test triggers; the two workflow files are ignored
- test_ci_changes.py: workflow-only set is 6 units; assert xks-remote triggers on XKS-related Rust sources
- ci-paths.toml: drop the windows toolchain set and cargo_test.ps1 from windows-cargo-test (ps1 now ignored); other windows-* units keep their feature triggers
- test_ci_changes.py: vcpkg, windows actions and the ps1 scripts never trigger no-nix or windows-cargo-test
- ChangedFiles: temp git repo (modify/add/delete, renames, merge-base, merge-commit HEAD^1, unknown ref)
- Main: report, compact skip= JSON, $GITHUB_OUTPUT append, fail-safe reasons, default and forwarded refs
- CommandLine and LoadConfig error messages; 84 tests, every statement of ci_changes.py executed
- temp-repo git runs with no global/system config and a fixed identity (no signing, hooks or missing-identity failure on runners)
- the subprocess runs drop GITHUB_OUTPUT so the self-test cannot add a stray skip= line to the changes step output
- ci_changes.py emits db-matrix, interop-matrix, run-test and run-windows next to skip; --all for non-PR events
- ci-paths.toml: `variants` per db:*/interop:* unit and a [callers] table
- test-db.yml / test-interop.yml build their matrix from the emitted legs; test_all.yml gates suites itself
- main.yml skips the whole test / windows call when none of its units runs
… link check out of main.yml

- ci-paths.toml: new build-documentation unit (documentation/, AGENTS.md, AI instruction files, docs tasks); main.yml build-documentation job gated on it
- linkcheck.yml: schedule-only workflow, so PRs no longer list a skipped link-check row
- CHANGELOG: fix the skip-units sentence that db/interop no longer take
- ci_changes.py emits a single suites-matrix [{suite, variant, bench}] built from the `variants` / `bench` of ci-paths.toml units; db-matrix and interop-matrix are gone
- test_all.yml: test-suites replaces test-db, test-interop, test-hsm, test-obs, test-pkcs11, test-pki and test-spire; per-leg secrets expressions limit EDB/IRIS to interop and Splunk to obs
- test-cloud and test-ui stay separate jobs so their secret scope is set by the job
- test-group.yml carries the database environment; test-db.yml and test-interop.yml are removed
- Wiring test: only `pki` may be both a test_all.yml job and a suites leg; `cloud` and `ui` must never get variants
- linkcheck.yml: job-level contents: read, persist-credentials: false
@Manuthor Manuthor closed this Nov 21, 2026
@Manuthor
Manuthor deleted the ci-probe-head branch November 21, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant