|GitHub Enterprise Adds Global Webhooks|
|Written by Kay Ewbank|
|Thursday, 14 December 2017|
There's a new release of GitHub Enterprise with new tools to help developer teams stay focused. Improvements include project board enhancements, global webhooks, and repository archiving.
GitHub Enterprise is designed to give large companies a way to deploy GitHub in their own environments. This means it can be used locally to manage custom apps designed for their own users. It offers commit histories, code browsing, compare views, pull requests, issues, wikis, gists, organizations and team management, all available locally, on your own server.
Project boards were already included in the previous version to help teams keep track of what’s happening with a group of tasks. The boards have now been improved with the addition of automation events that will update the status of your tasks for you automatically on the boards. If a developer carries out a task such as adding a new card to a project, closing an issue, or merging a pull request, the cards will automatically move between columns in real time.
Where tasks within project boards have external dependencies, another improvement means you can use notes to add links to those dependencies. This means that if you reference an issue or pull request in a note, you’ll now see a preview of the cross-referenced link in a summary card, making it clearer that an external link exists.Project boards have also been improved with support for keyboard shortcuts that can be used to navigate between cards and columns, to move cards and columns, and commit changes.
Webhooks are another area to have been enhanced, in this case by the addition of support for global webhooks.They are used within GitHub Enterprise to monitor, respond to, or enforce rules for user and organization management, but in the previous version they had to be defined per repository or organization. The new Global Webhook support means you can set up webhooks for an entire enterprise instance instead of one repository or organization at a time. This means admins will be notified about new users and organizations, deleted users and organizations, and membership changes.
Another area to have been improved is the organization of repositories, with support for archiving of older repositories when they're inactive, setting them to be read-only to owners and contributors. While no one will be able to add new issues, pull requests, or comments, the repository will still be available for later iteration.
The final main improvement is automatic HTTPS deployment. This has been achieved via support for Let’s Encrypt, a public Certificate Authority that automatically obtains and renews TLS and SSL certificates. Admins can get a secure “green HTTPS padlock” by running a simple CLI command or requesting a TLS certificate in the Management Console, with no fees or manual steps for certificate renewal.
or email your comment to: email@example.com
|Last Updated ( Thursday, 14 December 2017 )|