Repository navigation
Phase 1: permesh check, notifications and starter CI - #53
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an unattended review run that small IT teams can schedule in CI.
permesh check(experimental) collects a snapshot, evaluates review rules and writessnapshot.json,check.jsonand a counts-onlysummary.md. Exit codes: 0 clean, 6 needs review, 4 incomplete, 3 failed.--previous): new and removed admins come from the core admin query, so admin access gained through a team or group is caught. Identities that vanished are listed as "needs review", never as departed. A comparison that isn't comparable is inconclusive (exit 4). Without a comparison, change counts read "not compared", never zero.check.notificationsinpermesh.yamlfor Slack, Teams, a generic webhook, or email over SMTP (lettre with rustls/aws-lc-rs).detail: true.env:///keychain://references. Webhooks require https (plain http only on loopback); SMTP always uses TLS.permesh init --starterwritesexamples/starter: workspace template,ci/bootstrap.sh, a review policy, and SHA-pinned GitHub Actions plus GitLab CI workflows.permesh.yamlpin matches.gh attestation verify.summary.mdonly. Docs require a private repository.Validation: fmt, clippy
-D warnings,cargo test --all --locked, Python script tests,check_docs.py,cargo denyandcargo audit --deny warningsall pass, and actionlint is clean on the starter workflow.ci/bootstrap.shwas run against the real GitLab/Entra/Identity Center 0.2.0 packages, and a mismatched pin fails as intended. A fresh whole-branch review found one critical and six important issues, all fixed with tests.Not yet verified:
check; the workflows reference 0.1.0-alpha.4, which doesn't exist yet.