Pushing and pulling with an upstreamĮvery now and again, if I know I’ll be pushing and pulling a fair bit over the life of a feature (or setting up a ‘forever’ branch like develop or staging), setting an ‘upstream’ makes things quicker. That means I’m generally happy to write those longer commands when pushing and pulling. I tend to push my work up to the remote when it’s ready for PR (Pull Request), so my feature branches don’t typically live all that long once they’re on the remote repo. If you’re working with someone else, or have been working on the same branch from two separate machines, you can pull changes down like this: git pull origin my-great-feature To push more changes up there, just repeat the command. If a branch called my-great-feature doesn’t already exist up there, that command will create one with that name, based on your local branch. So if you’re checked out on a branch called my-great-feature you can push a branch of the same name to the remote like this: git push origin my-great-feature Pushing and pulling without an upstreamīy default, you can push and pull changes from any branch on your remote to the local branch you’re currently sitting on. What that means is you match a branch on your local development environment to a branch on the remote repository (repo), up in GitHub, GitLab or wherever. There’s no such thing as syncing in Git, but setting an upstream branch is about as close as it gets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |