CLOUDP-347875: Move GCI to go tool instead of Devbox#2752
Merged
Conversation
s-urbaniak
approved these changes
Sep 30, 2025
josvazg
approved these changes
Sep 30, 2025
helderjs
approved these changes
Sep 30, 2025
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.
Summary
GCI was causing issues with Devbox updates, so we can instead install it as a go tool and remove it from Devbox to circumvent the issue.
This does mean that we must invoke gci with
go tool- the only place I found we use gci was in the fmt make target, which I have updated.Proof of Work
Checklist
Reminder (Please remove this when merging)