GitHub Desktop is an open source Electron-basedGitHub app. It is written in TypeScript anduses React.
GitHub Desktop Focus on what matters instead of fighting with Git. Whether you're new to Git or a seasoned user, GitHub Desktop simplifies your development workflow. Download for macOS Download for Windows (64bit) Download for macOS or Windows (msi) Download for Windows. By downloading, you agree to the Open Source Applications Terms. GitHub Desktop is a tool that allows you to interact with GitHub from the desktop. With this new application, you can work easier without having to depend on your browser.
Download the official installer for your operating system:
You can install this alongside your existing GitHub Desktop for Mac or GitHubDesktop for Windows application.
NOTE: there is no current migration path to import your existingrepositories into the new application - you can drag-and-drop your repositoriesfrom disk onto the application to get started.
Want to test out new features and get fixes before everyone else? Install thebeta channel to get access to early builds of Desktop:
The release notes for the latest beta versions are available here.
There are several community-supported package managers that can be used toinstall GitHub Desktop:
c:> choco install github-desktop
$ brew install --cask github
Installers for various Linux distributions can be found on the
Arch Linux users can install the latest version from theAUR.
This document describes the focus of GitHub Desktop and who the product is most useful for.
And to see what the team is working on currently and in the near future, check out the GitHub Desktop roadmap.
Note: The GitHub Desktop Code of Conduct applies in all interactions relating to the GitHub Desktop project.
First, please search the open issuesand closed issuesto see if your issue hasn't already been reported (it may also be fixed).
There is also a list of known issuesthat are being tracked against Desktop, and some of these issues have workarounds.
If you can't find an issue that matches what you're seeing, open a new issue,choose the right template and provide us with enough information to investigatefurther.
If nobody has responded to your issue in a few days, you're welcome to respond to it with a friendly ping in the issue. Please do not respond more than a second time if nobody has responded. The GitHub Desktop maintainers are constrained in time and resources, and diagnosing individual configurations can be difficult and time consuming. While we'll try to at least get you pointed in the right direction, we can't guarantee we'll be able to dig too deeply into any one person's issue.
The CONTRIBUTING.md document will help you get setup andfamiliar with the source. The documentation folder also contains moreresources relevant to the project.
If you're looking for something to work on, check out the help wanted label.
See desktop.github.com for more product-orientedinformation about GitHub Desktop.
The MIT license grant is not for GitHub's trademarks, which include the logodesigns. GitHub reserves all trademark and copyright rights in and to allGitHub trademarks. GitHub's logos include, for instance, the stylizedInvertocat designs that include 'logo' in the file title in the followingfolder: logos.
GitHub® and its stylized versions and the Invertocat mark are GitHub'sTrademarks or registered Trademarks. When using GitHub's logos, be sure tofollow the GitHub logo guidelines.
GitHub Desktop 2.0 has officially been released. Since our 1.0 release, we’ve added more features to better support your workflows. You can resolve merge conflicts more easily, co-author commits to share credit with others, and check out your GitHub pull requests. And with the 2.0 release, rebasing and stashing are now also supported on GitHub Desktop—the two most requested features. As you’ve seen from GitHub more broadly, we’re focused on listening to our users and supporting the workflows you need to be most successful when building software. Whether you’re a seasoned developer or brand new to concepts like version control, GitHub Desktop puts the things you need most front and center.
From countless conversations with developers all over the world, we know that individual developers and teams have different ways of working. Our goal with GitHub Desktop 2.0 is to allow teams to work together collaboratively and support the most common development patterns we see when teams use GitHub. With GitHub Desktop, it’s easy to get up to speed and get productive with Git quickly, avoid common pitfalls, and learn the most critical underlying concepts as you gain more experience. As a result, we’ve seen adoption pick up among instructors and people who are new to version control.
It’s a common situation: you’re in the middle of reproducing and fixing a bug, and you need to switch context temporarily. Git branches are incredibly useful, but what do you do with your changes that are in progress? In Desktop 2.0, if you’re not ready to commit your work, you can choose to bring your changes to the new branch or keep them on your current branch.
Developers have also shared that many teams prefer a clean commit history without merge commits. This is a great example of where preferences dramatically differ. If you’re used to merging branches normally, you can still continue using the same workflow. But if you work in a repository where you don’t want those merge commits, Desktop 2.0 now supports rebasing to help you keep that commit history clean.
Most features we’ve released since GitHub Desktop 1.0 encourage collaboration, but collaboration doesn’t have to be tedious. Working together to create new things should be fun, and small things can make a big difference. Since 1.0, we introduced features that help foster a creative and supportive team dynamic—you can add emojis to commit messages, select a co-author of a commit just by mentioning their GitHub username, and push your work to GitHub with the suggested next step when you’re done committing. Sharing credit for work accomplished with others has never been easier.
As we reflect on our decision to open source the new version of GitHub Desktop, we’re genuinely grateful for the opportunity to work in the open and alongside our community contributors. Open source is in GitHub’s DNA. We’re proud to participate in the ecosystem that connects 36 million developers and advocate for the needs of open source maintainers internally. When it comes to open source, it truly takes a village, and we’re thankful for the hundreds of contributions we’ve received from over 150 community contributors. Thank you for making GitHub Desktop awesome.
Looking forward, you can expect to see more in GitHub Desktop that surfaces context from GitHub.com to help make you even more productive on your local machine. We’re taking the first step by tightly integrating pull requests between GitHub and Desktop. You can easily open any pull request from GitHub.com in GitHub Desktop and have everything ready to go locally. You’ll be able to test things out, add more commits, or take a closer look at the code on your machine during a review. And now it’s much easier to create a pull request in GitHub Desktop using suggested next steps.
Millions of people have downloaded GitHub Desktop with more than 500,000 people actively developing in the app each month. We’ve now built out many of the highest impact and most requested local Git workflows. Now we’re focusing on extending GitHub.com features even further to provide you with a seamless experience native to your workflow. We hope to continue to lower the barriers to entry so that millions more can participate in software development, research, design, and more. If you’re on the fence about whether to start or continue building technology, we want to make it easier with GitHub Desktop.