Avoid gofumpt'ing other worktrees - #5931
Merged
Merged
Conversation
This is usually not a problem (except for the unnecessarily wasted time) because all worktrees should normally be correctly formatted; but it is a problem when we bump the formatter version, and some worktrees are already on the new version and others still on the old.
stefanhaller
force-pushed
the
avoid-gofumpting-other-worktrees
branch
from
August 14, 2026 20:44
837d700 to
1a3cf79
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is usually not a problem (except for the unnecessarily wasted time) because all worktrees should normally be correctly formatted; but it is a problem when we bump the formatter version, and some worktrees are already on the new version and others still on the old.