Skip to content

docs: document signed-merge policy (squash/merge, not rebase)#2

Merged
aray-17 merged 1 commit into
mainfrom
docs/signing-merge-policy
Jun 15, 2026
Merged

docs: document signed-merge policy (squash/merge, not rebase)#2
aray-17 merged 1 commit into
mainfrom
docs/signing-merge-policy

Conversation

@aray-17

@aray-17 aray-17 commented Jun 15, 2026

Copy link
Copy Markdown
Owner

What

Adds a Merging section to CONTRIBUTING.md: main is kept signed/Verified on GitHub, so PRs should be merged with Squash and merge or Create a merge commit (both GitHub-signed). Rebase and merge re-creates the merged commit without a signature.

Why

PR #1 was merged via rebase, which left its merged commit (ff5d296) unverified on main. Re-signing an existing commit requires a force-push, which main's branch protection (mirrored from agent-capsules) correctly blocks. Documenting the merge method prevents recurrence — and merging this PR via squash or merge-commit restores a signed/Verified HEAD on main.

Note on merging this PR

Please merge with Squash and merge or Create a merge commit (not Rebase) so the new HEAD is GitHub-signed.

🤖 Generated with Claude Code

main is kept signed/Verified on GitHub. Rebase-merge re-creates the merged
commit without a signature (it left one unverified commit on main); squash
and merge-commit are GitHub-signed. Document the policy in CONTRIBUTING so
future merges keep main verified.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aray-17 aray-17 merged commit 6491373 into main Jun 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant