GitHub released GitHub Desktop 3.0, improving the pull request and notification features. Some developers backed the update and said it will make life easier; for others, Desktop 3.0 missed the mark, with sought-after features still missing from the platform.
The update added the ability to review the status of pull request verification runs and view important notifications. Some software developers welcome the new additions, including prioritization of team member notifications and the ability to view pull request checks to ensure code is ready for production.
“For the onboarding of new contributors to Camunda Community Hub projects, updating GitHub can have a big impact,” said Amara Graham, director of developer experience at Camunda, a code workflow and decision automation platform. opened. “New collaborators They may not have their GitHub notifications configured in such a way that they see things like failed checks, and pointing them to the GitHub desktop experience should help reduce our back-and-forth on the pull request to merge.”
Others, however, have described the launch as lackluster. They want to see better cross-platform connectivity, pre-populated information on pull requests, and storage improvements.
Software developers at Redgate, a provider of DevOps-enabled database software in Cambridge, England, said Desktop 3.0 it has little to offer developers with already implemented workflows.
“The update is not relevant,” said Jeff Foster, Redgate’s chief product engineer. That’s because most of its developers use the Git command line or an IDE integration, he said.
Grant Fritchey, a DevOps product advocate at Redgate, was also unimpressed with version 3.0. “I don’t think GitHub Desktop is going to change my life much,” he said of the release.
Welcome additions to GitHub Desktop
GitHub Desktop 3.0 informs developers specifically why a check failed. Kimberly Silva, Senior Software Engineer and CEO of FindPeopleFirst, a people search service, finds this new functionality useful because it allows developers to attempt to resolve transient verification issues without leaving the application.
Silva isn’t the only developer to find value in the new feature. “This adds more convenience to my work and reduces the number of places I have to check when working with the repository,” said Olena Kutsenko, developer and software engineer at Aiven, a multinational open source data cloud company. “In other words, it helps me focus on the tasks at hand.”
Consolidating troubleshooting and security analysis gives developers the ability to more easily remediate vulnerabilities before sharing the work, said Ankur Papneja, product manager at Contrast Security, an application security company. “This means developers will be more productive,” he said.
Another welcome feature is the improved notification process. In previous versions of GitHub Desktop, software developers had to go through hundreds of notifications for every event in every repository, most of which were noise. The enhanced feature will make it easier for developers to keep track of code changes and requests, Silva said.
Desktop 3.0 lacks important features
grant fritcheyDevOps Product Advocate, Redgate
But other developers said version 3.0 doesn’t go far enough. One feature developers would like to see is better cross-platform connectivity, which is a crucial need for developers working on more than one platform. Fritchey, who interacts primarily through VS Code or the command line, said, “If I can properly connect to Git remotely on AWS CodeCommit, I’ll have their children.”
Graham would like to see a link to create a pull request that includes pre-populated information about verification failures. If this information floats to the exact spot where the check failed, the reviewer can respond faster, he said.
As for Silva from FindPeopleFirst, he would like to see a specific UI for creating a stash with a customizable name, adding that another useful addition would be the ability to create a commit template with preset text that can be reused for many commits. “These features will reduce silos of work,” she said, “giving developers who prefer to work on multiple files more flexibility.”
Future updates are likely to bring more improvements
Despite the lukewarm reception of the update, there is optimism that GitHub will fix many of these issues in future updates.
“Microsoft has done a great job of upholding GitHub’s open source stance,” said Larry Carvalho, independent analyst at RobustCloud. He added that the GitHub Desktop initiative is supported by a large community of developers who provide feedback on which features are a priority, indicating that future updates to GitHub Desktop will continue to be based on developer needs and wants.