Fetch latest origin as part of deploy PR script#11563
Merged
Conversation
changelog: Internal, Deploy, Fetch latest origin as part of deploy PR script
mitchellhenke
approved these changes
Nov 26, 2024
matthinz
approved these changes
Nov 26, 2024
amirbey
approved these changes
Nov 26, 2024
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
4 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.
🛠 Summary of changes
Updates
scripts/create-deploy-prto run fetch the latestgitremote before starting the script.If the deployer hasn't recently fetched the remote repository, they can often encounter a cryptic error when trying to create the branch based on the latest commit in the staging environment.
Related Slack discussion: https://gsa-tts.slack.com/archives/C0NGESUN5/p1719949060382589
📜 Testing Plan
Run
DRY_RUN=1 scripts/create-deploy-prand verify no errors in output