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 kommentar(er)
