entireio / entireio/cli

Community Discord feedback: Entire-Checkpoint trailer is too noisy in GitHub commit UI

Open
#868 0 comments 0 reactions 1 assignee View on GitHub

@blackgirlbytes is already working on this.

Since Apr 9, 2026.

enhancement
Dominant language
Go
Stars
5.1k
Forks
475
Avg merge
1d 11h
Merged PRs (30d)
178

Description

Context

This issue captures community feedback from Discord:

Discord thread

A community member pointed out that the Entire-Checkpoint: ... trailer is too noisy in GitHub’s commit UI and would prefer for it to be removable or hidden.

Current behavior

Today, the trailer is the durable link between a user commit and Entire checkpoint metadata.

  • If the trailer is present, the commit stays linked.
  • If the trailer is removed, the linkage is skipped.
  • GitHub may surface that trailer in the commit’s extended description.

Constraint

The current trailer-based approach appears intentional: the linkage survives amend/rebase/squash workflows because it travels with the commit message.

Because of that, there may not be a meaningful git-level alternative here that preserves the same durability.

Possible Solutions

  • Keep the current behavior and treat this as a known tradeoff.
  • Explore GitHub-side presentation solutions, such as a browser extension that hides Entire-Checkpoint: lines in the GitHub UI.
  • Explore a GitHub-side enhancement that both hides the trailer and optionally adds a link from the commit UI to the Entire checkpoint page.
  • Revisit whether there is any durable non-trailer metadata approach worth considering, understanding that it may not survive amend/rebase/squash workflows reliably.

Status

Captured community feedback only. This issue should not be interpreted as an active implementation commitment.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.