You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Governance config: reference_audiences per entity kind (default for cus: contracts and mgmt), governance.owner_teams in kh.yaml, and the owners.yml model with CODEOWNERS rendering.
kh governance render writes the frontmatter JSON Schema, owners.yml, CODEOWNERS, the pull request template and the kh Forgejo workflow for a canonical repository.
Forgejo client: compare files, branch head lookup, team and membership reads, and post_status guarded to the kh/validate and kh/domain-owners contexts.
kh validate --repo R --base B --head H checks the markdown files a pull request changes in a canonical repository, prints one path: reason line per problem, exits 0, 1 or 2 and posts the kh/validate commit status. Ids are checked only across the repos the token can read (unreadable ones are skipped), no Grist table is read for a kind the repo may not cite, and errors never name another repository.
kh governance render --runner-label sets the runner label of the rendered workflow, so each audience can have its own runner (default kh-validate:host).
kh domain-owners --repo R --pr N checks that the teams named in owners.yml (and, for a widen-audience/<audience> label, the audience's owner teams) have approved the current head of a pull request, prints one line per missing approval and posts the kh/domain-owners commit status.
self_merge_teams in kh.yaml: a merged pull request is also trusted when its author, a member of a team that owns every touched path in owners.yml, merged it themselves. Such documents carry the new stamp owner_merge.
stamp (reviewed, owner_merge, anchor or empty) in search and get_doc results, next to approved_by; stamp is a forbidden frontmatter key.
Merge verdicts are stored in kh.merge_verdicts and reused by every sync and rebuild; kh rebuild --rejudge judges every merge afresh.
bot_logins in kh.yaml (default [kh-hub-bot], which is always included): bots never self-merge and their approvals never count.
kh domain-owners passes a pull request whose author may self-merge as owner.
Changed
kh domain-owners prints the approval or self-merge that applied when it passes.
An audience list in entities.<kind>.audiences or raw_audience_map now means any one of the audiences may read the rows; derived records, candidates and conflicts still need every source. Check multi-audience lists before upgrading (migration 0007).
generated_by and derived_from are forbidden frontmatter keys, like the other keys the server writes.
The indexer skips paths with a dot-prefixed segment, so .forgejo/pull_request_template.md raises no alert.
The PrivacyFence declaration example sets email_for_visibility: true.