chore: trim verbose comments in shrinkwrap script and release workflow - #9435
Merged
Merged
Conversation
Contributor
zahin-mohammad
approved these changes
Aug 6, 2026
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
3 participants
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.
Ticket: WCI-1274
Summary
Pure comment cleanup, no behavior change. Addresses code-review feedback on the WCI-1270 shrinkwrap/two-phase-publish work: the explanatory comments I wrote across
scripts/generate-bitgo-shrinkwrap.tsand the release workflows were "way too verbose... limit to a few lines at most." This PR trims them down while keeping the one non-obvious "why" in each spot.