![]() ![]() " Microsoft has done a great job in maintaining the open source posture of GitHub," said Larry Carvalho, an independent analyst at RobustCloud. "These features will reduce work silos," she said, "giving developers who prefer to work on various files more flexibility." Future updates likely to bring more improvementsĭespite the lukewarm reception to the update, there is optimism that GitHub will fix many of these issues in future updates. If this information floats up to the exact place where the check failed, the reviewer may be able to respond faster, she said.Īs for FindPeopleFirst's Silva, she 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. Graham would like to see a link to create a pull request that includes pre-populated information about check failures. Fritchey, who mainly interfaces through VS Code or the command line, said, "If you can get me connected properly to Git remotely in AWS CodeCommit, I'll have your children." One feature that developers would like to see is better cross-platform connectivity, which is a crucial need for developers working on more than one platform. Grant FritcheyDevOps product advocate, Redgateīut other developers said the 3.0 version doesn't go far enough. If you can get me connected properly to Git remotely in AWS CodeCommit, I'll have your children. The improved feature will make it easier for developers to keep track of code changes and requests, Silva said. In prior versions of GitHub Desktop, software developers had to sift through hundreds of notifications for every event in every repository - most of which were noise. "This means that developers will become more productive," he said.Īnother welcome feature is the improved notifications process. The consolidation of issue resolution and security analysis gives developers the ability to remediate vulnerabilities more easily before sharing work, said Ankur Papneja, product manager at Contrast Security, an application security company. "In other words, it helps me focus on my tasks at hand." "This adds more convenience to my work and decreases the number of places I have to check when working with the repository," said Olena Kutsenko, a developer and software engineer at Aiven, a multinational open source data cloud company. Silva isn't the only developer finding value in the new feature. Kimberly Silva, senior software engineer and CEO at FindPeopleFirst, a people finder service, thinks this new functionality is helpful because it enables developers to try and resolve transitory check issues without exiting the app. ![]() GitHub Desktop 3.0 informs developers specifically why a check failed. "I don't think GitHub Desktop is going to change my life much," he said about the release. Grant Fritchey, a DevOps product advocate at Redgate, was also less than impressed the 3.0 version. That's because most of its developers use the Git command line or an IDE integration, he said. "The update isn't relevant," said Jeff Foster, head of product engineering at Redgate. Software developers at Redgate, a software provider for compliant database DevOps in Cambridge, England, said that Desktop 3.0 has little to offer for developers with workflows already in place. They want to see better cross-platform connectivity, pre-populated information in pull requests and stash improvements. ![]() Others, however, have described the rollout as lackluster. " New contributors may not have their GitHub notifications set up in such a way to see things like failed checks, and pointing them to the GitHub Desktop experience should help reduce our back-and-forth dialogue on the pull request itself to get it merged." "For onboarding new contributors into Camunda Community Hub projects, GitHub's update may be hugely impactful," said Amara Graham, head of developer experience at Camunda, an open source workflow and decision automation platform. Some software developers welcome the new additions, including prioritizing notifications from team members and the ability to see checks for pull requests to make sure code is production-ready. The update added the ability to review the status of pull request check runs and view important notifications. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |