Tim Abbott (Dec 05 2016 at 21:53): Tim Abbott (Dec 05 2016 at 21:53):I've noticed that frequently students are closing pull requests and creating new ones when they want to push an updated version of there changes. With Git and GitHub, you should essentially never need to do this. Further, doing so makes more work for the maintainers and slows the review of your work, since we then need to look at the old PR to see what the comments you were attempting to resolve in making revisions to your pull request. Instead, you should always being using a git force-push to update the remote branch the PR was based off of. If you decide to restart a local branch as part of making your revisions, that's fine, you just need to use the more complicated git push origin +localbranchname:remotebranchname to push your changes. The maintainers of any open source project you contribute to will appreciate it!
Steve Howell (showell) (Dec 05 2016 at 21:57):I've been suggesting this, which I think is consistent with our docs:
git push origin +my-feature-branch-name
Tim Abbott (Dec 05 2016 at 21:58):yes, that doesn't work if they created a new feature branch name locally for their revisions, however
Tim Abbott (Dec 05 2016 at 21:58):So the more advanced syntax can be necessary in some cases
Last updated: Jul 19 2022 at 08:22 UTC