This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

A stale remote branch carrying a secret literal fails the gitleaks gate on every open pull request, and deleting the branch is the only remedy: the CI job checks out with fetch-depth 0, which fetches every remote ref, so 'gitleaks git' scans all of them rather than the pull request's own history. A literal committed on a branch whose pull request was closed and superseded therefore keeps failing unrelated pull requests, and the failure names neither the branch nor the file when the run log truncates the findings, so the natural diagnosis (a leak in this pull request) is wrong. Observed 2026-08-28: commit 9ffbbfbc on the superseded branch of a closed pull request blocked all seven open pull requests until the branch was deleted. Worth either scoping the scan to the pull request's own commits, or adding a cleanup gate that refuses to leave a leaking branch on the remote after its pull request closes.

issueresolvedmajoriss-2608282038283692

A stale remote branch carrying a secret literal fails the gitleaks gate on every open pull request, and deleting the branch is the only remedy: the CI job checks out with fetch-depth 0, which fetches every remote ref, so 'gitleaks git' scans all of them rather than the pull request's own history. A literal committed on a branch whose pull request was closed and superseded therefore keeps failing unrelated pull requests, and the failure names neither the branch nor the file when the run log truncates the findings, so the natural diagnosis (a leak in this pull request) is wrong. Observed 2026-08-28: commit 9ffbbfbc on the superseded branch of a closed pull request blocked all seven open pull requests until the branch was deleted. Worth either scoping the scan to the pull request's own commits, or adding a cleanup gate that refuses to leave a leaking branch on the remote after its pull request closes.

Grounds

  • pursued: a secret on a branch that is not an ancestor of the checked-out commit no longer fails the scan, while one in the landing history still does; shown wrong by a CI gitleaks failure whose finding sits only on another ref

Frontmatter

idiss-2608282038283692
typeissue
lifecycleresolved
severitymajor