Pull latest changes on redeploy instead of skipping - #26
Merged
Conversation
setup.sh skipped git clone entirely whenever the project directory already existed, so a redeploy never fetched new commits pushed since the first deploy. Run git pull in that branch instead.
copelco
approved these changes
Aug 27, 2026
copelco
left a comment
Member
There was a problem hiding this comment.
Pulled new changes for me! Nice
Cloning repository...
Directory dsd-testproj already exists. Pulling latest changes...
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.
setup.shskippedgit cloneentirely whenever the project directory already existed, so a redeploy never fetched new commits pushed since the first deploy. Run git pull in that branch instead.This was generated with the help of Claude based on some friction points of attempting to deploy to PythonAnywhere repeatedly.