Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,12 +194,20 @@ Typical scopes match the modules: `base`, `warrant`, `access`, `echo`,

### Signed commits

All commits must be **signed**. Use the existing SSH/GPG signing key; do
not create new keys. Verify with:

git log --show-signature

Unsigned commits will be asked to be re-signed before merge.
Every commit that reaches the default branch must be signed; a ruleset refuses
unsigned pushes. Estate policy:
[SIGNING-POLICY](https://github.com/hyperpolymath/standards/blob/main/docs/SIGNING-POLICY.adoc).

- **People and interactive agents** sign with an SSH key registered on GitHub
as a *signing* key (`gpg.format=ssh`, `user.signingkey=<key>.pub`,
`commit.gpgsign=true`). The committer email must be verified on that account.
- **Apps, bots and workflows** never `git push` local commits. They write
through the API (`createCommitOnBranch` or the estate `signed-push` action)
so that GitHub signs each commit.
- Merge PRs with **squash**. The ruleset checks every commit on the PR branch,
not just the result, so one unsigned commit blocks the merge. Re-create such a
branch with signed commits (`git cherry-pick -S`) and open a new PR.
Rebase-merge replays commits unsigned and is disabled.

### Before you open a PR

Expand Down
Loading