Repository navigation
chore: setup-github-token gativ2 rollout - 20% allocation - #1679
Merged
Merged
Conversation
Contributor
🦋 Changeset is good to goLatest commit: 3e0d20a We got this. Not sure what this means? Click here to learn what changesets are. |
Tofel
approved these changes
Oct 2, 2026
chainchad
approved these changes
Oct 2, 2026
Merged
This was referenced Oct 21, 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
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 dials up the allocation to GATI v2 migration from
0%to20%.Notes
$GITHUB_REPOSITORY) (deterministic hash)Rollback Instructions
git fetch --tags --force- ensure your tags are up to dategit tag -f setup-github-token/v1 setup-github-token/1.3.0- retag it to the version with 0% allocationgit push origin --force setup-github-token/v1- force push the retag