Skip to content

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

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aray-17 merged 1 commit into from
Jun 15, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,14 @@ The offline suite uses scripted adapters — no API keys required. Live
evaluation against real models, and the SWE-bench Docker path, are
reserved for separate benchmarking and are not part of CI.

## Merging

Commits and tags on `main` are signed (SSH) and show as **Verified** on
GitHub. To keep `main` fully verified, merge pull requests with **Squash
and merge** or **Create a merge commit** — GitHub signs the resulting
commit automatically. Avoid **Rebase and merge**: it re-creates the
commit without a signature, leaving an unverified commit on `main`.

## Evaluation methodology and operational data

A larger body of operational evaluation work — per-instance stream
Expand Down
Loading