Skip to content

docs(fork): name the merged commits of the snapshot-tar rows - #261

Merged
teemow merged 1 commit into
giantswarmfrom
fork/ledger-2110-2111
Oct 10, 2026
Merged

teemow merged 1 commit into
giantswarmfrom
fork/ledger-2110-2111

Conversation

@teemow

@teemow teemow commented Oct 10, 2026

Copy link
Copy Markdown
Member

Problem

The two FORK.md rows carried from upstream's PATH_MAX-safe snapshot tars (agent-substrate#2110 and agent-substrate#2111, #260) name only their pull request in the "Fork commit" column. Every other row names the commit as it is on the line and the first release carrying it.

Proposed solution

Name the rebase-merged commits 3afd756f (agent-substrate#2110) and eb04dfc1 (agent-substrate#2111), the merge date and the first release, 1.8.0-rc.6, in the same shape as the other rows.

Acceptance criteria

  • Both rows name their commit on giantswarm, the pull request, the merge date and the first release.
  • The ledger check passes (a docs(fork) edit of FORK.md alone needs no row of its own).

Opened by an agent on behalf of Timo Derstappen.

The two rows carried from upstream's PATH_MAX-safe snapshot tars named
only their pull request. They now name the rebase-merged commits on the
line and the first release that carries them, as every other row does.

Signed-off-by: Timo Derstappen <teemow@gmail.com>
@teemow
teemow requested a review from a team as a code owner October 10, 2026 11:47
@teemow
teemow merged commit d7666f1 into giantswarm Oct 10, 2026
17 checks passed
@teemow
teemow deleted the fork/ledger-2110-2111 branch October 10, 2026 12:07
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