In GitHub Desktop 3.1, we introduced viewing the diff of changes across multiple commits. This allows you to be certain there are no unintended changes in the group of commits you are about to push. 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.
GitHub Desktop 3.1.5 improves support for force pushing and fetching through the newly added Repository menu items as well as supporting pull request notifications on forks. This release also comes with many great contributions (12 changelog entries!
Previously, a user could only force push after an action such as rebasing. Now, when users find their branch in any diverged state, they can opt to use the force push Repository menu item. For example, a user can force push when commits exist on the remote that they are sure they want to overwrite.
Similarly, a user may find themselves in a new local branch they are not ready to publish, yet they want to fetch to see if there are any new changes on their main branch they would want to merge in. Instead of having to switch branches, they can use the Repository menu item to fetch those changes.
If you have been enjoying our Pull Request notifications on your repositories, you will be happy to hear that with 3.1.5 those same notifications are supported on forks.
We love the help we get from the open source community, providing many fixes and improvements for everyone to enjoy.
Thank you @angusdev for contributing all these fixes:
Thank you @tsvetilian-ty for adding support for JetBrains Toolbox and JetBrains Fleet editor for Windows.
Thank you @zipperer for adding support for emacs editor.
Thank you @patinthehat for adding support for JetBrains PhpStorm and WebStorm editors
Thank you @daniel-ciaglia for adding support for VSCodium as an external editor.
Thank you @Shivareddy-Aluri for adding the ability to copy tag names from the commit list.
Thank you @j-f1 for improving the the diff view by adding highlighting to Arduino's .ino files as C++ source.
GitHub Desktop 3.1 improves submodule support and now supports multi-commit diffing.
Submodule support just got much better from GitHub Desktop by providing a more detailed “diff” when they have changes. You will now know whether submodules are just pointing at a different commit or if there are changes within them that you must commit. You can also open the submodule at the click of a button!
You can now also see all the changes across multiple commits by just selecting them. That way, you can be certain about the changes you’re about to push or merge onto another branch, and make sure no unintended changes are included in them.
GitHub Desktop 3.0.6 brings a slew of community contributions! As an open source project, we are always so grateful to our contributors who make Desktop better for themselves and others. Additionally, we’ve improved the recognition of default branch changes.
GitHub Desktop 3.0 is bringing a closer integration with GitHub pull request workflows.
GitHub Desktop now supports reviewing the statuses of individual check runs for a pull request directly in GitHub Desktop. This includes statuses of job steps for check runs generated through GitHub Actions. Customers can review the results of check runs on a PR, re-run jobs, and quickly navigate to the logs on github.com.
GitHub Desktop 2.8.2 now offers a native build for Apple silicon machines that use Apple's new M1 chip.
You can install it immediately from the GitHub Desktop site, and in upcoming releases Desktop will upgrade to the native build automatically.
GitHub Desktop 2.8 now allows you to:
Learn more about each of these new features and see them in action in today's blog post.
GitHub Desktop 2.7 includes cherry-picking interactively via drag and drop or via a context menu. A few additional features related to cherry-picking include:
Learn more about GitHub Desktop, or check out the full blog post about cherry-picking.
