Skip to content

docs: the record says how many trailers the landed commit carries, and it says one #76

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
github-actions merged 1 commit into from
Oct 30, 2026
Merged

docs: the record says how many trailers the landed commit carries, and it says one #76

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
16 changes: 13 additions & 3 deletions CHANGELOG/2026.303.0348.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,11 +234,21 @@ Harness `Claude Code`, model `minimax/minimax-m3.1-flash:cloud` — the pair the
change is prose-only, so the tier is the prose tier: `documentation reviewed`. The runtime gates
above were run and are pasted in full, but a runtime tier is not claimed for a comment-only change.

**Two trailers, honestly.** The branch's own content commit `7e4d5fd` was authored in an earlier
**The trailers, measured.** The branch's own content commit `7e4d5fd` was authored in an earlier
session and keeps ITS trailer (`DeepSeek Harness deepseek-v4.1-flash`); the pushed head `1756c8c`
is a merge commit written by this session and carries this session's trailer. GitHub's squash
is a merge commit written by this session and carries this session's trailer. **MEASURED on the
landing: GitHub's squash composes the landed message from the branch's NON-MERGE commit messages
only, so the landed commit `ee7962bb` carries ONE trailer — the content author's — and the merge
commit's message, with this session's trailer, is not carried into it.** The landed attribution is
the content author's, which is correct for the change the commit carries.

*Corrected after the merge.* The sentence that introduced this section said *"GitHub's squash
composes the landed message from the branch's commit messages in order, so the landed commit
carries both — each session's own authorship, neither overwritten.
carries both — each session's own authorship, neither overwritten"*, which was false: GitHub composes
the squash message from the branch's **non-merge** commit messages, so the landed commit `ee7962bb`
carries ONE trailer — the content author's — and the merge commit `1756c8c`'s own message, with the
takeover session's trailer, is not carried into it. The measurement was taken on the landing itself,
and the wording was corrected here — in the record, not only in the pull request.

Agent: charly

Expand Down