#GITHUB DESKTOP CODE#
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. You can easily open any pull request from in GitHub Desktop and have everything ready to go locally. We’re taking the first step by tightly integrating pull requests between GitHub and Desktop. Looking forward, you can expect to see more in GitHub Desktop that surfaces context from to help make you even more productive on your local machine. Thank you for making GitHub Desktop awesome.
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. We’re proud to participate in the ecosystem that connects 36 million developers and advocate for the needs of open source maintainers internally. Sharing credit for work accomplished with others has never been easier.Īs 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. 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. Working together to create new things should be fun, and small things can make a big difference. Most features we’ve released since GitHub Desktop 1.0 encourage collaboration, but collaboration doesn’t have to be tedious. 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. If you’re used to merging branches normally, you can still continue using the same workflow. This is a great example of where preferences dramatically differ. 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.ĭevelopers have also shared that many teams prefer a clean commit history without merge commits. It’s a common situation: you’re in the middle of reproducing and fixing a bug, and you need to switch context temporarily. As a result, we’ve seen adoption pick up among instructors and people who are new to version control.
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. 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. 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.įrom countless conversations with developers all over the world, we know that individual developers and teams have different ways of working. 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. And with the 2.0 release, rebasing and stashing are now also supported on GitHub Desktop-the two most requested features. You can resolve merge conflicts more easily, co-author commits to share credit with others, and check out your GitHub pull requests. Since our 1.0 release, we’ve added more features to better support your workflows. GitHub Desktop 2.0 has officially been released.
0 kommentar(er)
