Skip to content

docs: add Signed commits section to CONTRIBUTING #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 2 commits into from
Sep 30, 2026
Merged

docs: add Signed commits section to CONTRIBUTING #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b5987d
docs: add Signed commits section to CONTRIBUTING
hyperpolymath Sep 30, 2026
1f8ca3d
docs: tidy Signed commits section
hyperpolymath Sep 30, 2026
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
15 changes: 15 additions & 0 deletions .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,3 +86,18 @@ We follow [Conventional Commits](https://www.conventionalcommits.org/):

[optional footer]
```

## Signed Commits

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`, `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`, the estate `signed-push` action, or a
squash merge) so that GitHub signs the commit.
- Merge PRs with **squash**. Rebase-merge replays commits unsigned and is
disabled.
Loading