sneak/sfdupes
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

next #50

Open
clawbot wants to merge 1 commits from next into main
pull from: next
merge into: sneak:main
Conversation 0 Commits 1 Files Changed 4 +19 -7
clawbot commented 2026-08-10 16:07:56 +02:00
Collaborator
Copy Link

Long-lived next branch for the current cycle; one issue-closing commit
per work unit.

  • 337b319 Normalize the lint-image pin comments and FROM form
    (closes #25) — both lint
    images now carry the policy-form version/date comment and the bare
    FROM image@sha256:... form, dropping a parenthetical that asserted
    a base-image change that never happened. Digest unchanged.
Long-lived `next` branch for the current cycle; one issue-closing commit per work unit. - `337b319` Normalize the lint-image pin comments and `FROM` form (closes https://git.eeqj.de/sneak/sfdupes/issues/25) — both lint images now carry the policy-form version/date comment and the bare `FROM image@sha256:...` form, dropping a parenthetical that asserted a base-image change that never happened. Digest unchanged.
clawbot added 1 commit 2026-08-10 16:07:56 +02:00
Normalize the lint-image pin comments and FROM form (closes #25)
All checks were successful
check / check (push) Successful in 1m9s
Details
337b319542 
The `(Debian-based)` parenthetical broke the required
`# image:vX.Y.Z, YYYY-MM-DD` form and asserted a base change that never
happened (v2.12.1 was Debian too); the tag before the digest left three
FROM lines in one file using two conventions. Digest unchanged, in both
Dockerfile and Dockerfile.lint. The golang and alpine pin comments
already matched the required form.

script/verify-lint-image-pin parses these two FROM lines to keep them
identical and still matches the tagless form; its advice line drops the
now-meaningless "tag and digest". With no tag in either reference a
tag-only disagreement cannot arise; a tag reintroduced on one side is
caught as a plain mismatch.
clawbot added the needs-review label 2026-08-10 16:08:01 +02:00
clawbot self-assigned this 2026-08-10 16:08:01 +02:00
All checks were successful
check / check (push) Successful in 1m9s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin next:next
git checkout next
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
merge-ready
Review passed; ready to merge
 needs-checks
CI checks failing or not yet green
 needs-rebase
Branch conflicts with main; rebase required
 needs-review
PR awaiting independent adversarial review
 needs-rework
Review found blocking problems; author must rework
No Label needs-review
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
clawbot sneak
No Assignees clawbot
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/sfdupes#50
Delete Branch "next"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?