Repository navigation
feat: Sato Check Team mode (v1.4) — keyed repo inventory, org policy, SARIF - #6
Merged
Merged
Conversation
… SARIF With a Sato API key (input sato-api-key or env SATO_API_KEY) the Action registers the repo in the account's inventory, applies the org policy on top of the repo's .sato/policy.json (a repo can only tighten), records the run and uploads the merged-policy SARIF to code scanning. It fails open: only a policy rule the team wrote can fail the job. No key: nothing is registered or stored; behaviour is unchanged. Keeps v1.3.1's x-sato-repo own/not-own header and template-drift mode. UA satohub-preflight-action/1.4. 39 offline tests pass.
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
1 participant
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.
With a Sato API key (
sato-api-keyinput orSATO_API_KEY), the Action registers the repo in the account inventory, applies the org policy on top of the repo.sato/policy.json(a repo can only tighten), records the run and uploads the merged-policy SARIF to GitHub code scanning (needssecurity-events: write).x-sato-repoown/not-own header and template-drift mode).package.jsonmanifests in this release.satohub-preflight-action/1.4.Server side is live on satohub.ai (Sato Check Team plan). 39 offline tests pass.
Release plan: tag
v1.4.0after merge; movev1only after a dogfood week is green.🤖 Generated with Claude Code