For example, you can force push when commits exist on the remote that you are sure you want to overwrite. Now, when you find your branch in any diverged state, you can opt to use the force push repository menu item. Previously, you could only force push after an action such as rebasing. Since our last blog post, we have had a plethora of great enhancements released, including improved submodule support, notifications for forks, multi-commit diffing, force pushing, and fetching. It lets you do that double-checking before leaving your local development environment. ![]() ![]() Now with the “Preview Pull Request” feature, you can see the diff of all the changes brought in from all the commits on your feature branch before opening your pull request. Have you ever submitted a pull request only to find you’ve accidentally left in a debugger statement, requiring you to return back to your local environment, remove the debugger, commit, and push up the change? This can be annoying, time consuming, and maybe even a little embarrassing. If you find yourself apprehensive to push your changes up to and open a pull request, you will like the confidence boost reviewing your pull request locally will give you. GitHub Desktop helps you feel confident in your Git workflows, and now we want to help you feel confident in your GitHub workflows as well. ![]() Taking that feature to the next level, GitHub Desktop 3.2 allows you to “Preview your Pull Request”– see a diff of all the changes being introduced by your feature branch into your repository’s default branch. This allows you to be certain there are no unintended changes in the group of commits you are about to push. In GitHub Desktop 3.1, we introduced viewing the diff of changes across multiple commits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |