- Deployments API integrates with GitHub Flow.
- Integrator links can be expanded with relevant details in the context of GitHub comments via API.
- Only pull request authors or users with write access to repository can resolve conversations.
- Repository administrator can delete issues.
- Users can subscribe to only receive repository notifications for releases.
- Organization administrators can control whether users can create public, private, or no repositories.
- A timeline event is shown when users force push to a branch.
- Users can filter Pull Request by file type or hide deleted files.
- Repository administrators can transfer an issue to another repository where the administrator also has repository administration privileges.
- ‘Allow members to invite external collaborators’ setting added to Organization Settings page.
- Pull request reviews automatically update the merge button.
- 2-up image diffs will now also display file size alongside the width and height data.
- When hovering over the status of a commit in a pull request's timeline, the full details for that status is displayed in a popover.
- When searching from a user profile page users have the option to search by "this user".
- Users can pre-fill values in the new Release form fields using URL query parameters.
- Filtering files in a pull request by file type.
- Bookmark any notification to move it into a prioritized list called Saved for Later.
- When writing a comment with -1 or +1, GitHub suggests leaving a reaction.
- Maintainers can add more template automation in the form of a default title, labels, and assignees.
- When a user clicks the "Fork" button on a repository that has been already forked, the user's existing forks are listed.
- Create and upload file to empty repos.
- The native browser tooltip overlaid the GitHub custom tooltip when a commit message contained
Closes #issue text.
- The repository selection radio button and dropdown selection could be hidden when installing a GitHub App.
- Recent changes to a project board will be highlighted since a user's last visit.
- When viewing recent activity on a personal dashboard, timestamps will include a deep link to the most recent comment.
- The owner dropdown is highlighted first on the "Create a new repository" page.
- The keyboard shortcuts help dialog modal has been redesigned.
- Comments are only outdated when the line the comment is related to changes.
- New installs of Enterprise Server will use GitHub's NTP server pool by default and the upgrade package will change old default servers to the new NTP pool.
Backups and Disaster Recovery
GitHub Enterprise 2.16 requires at least GitHub Enterprise Backup Utilities 2.16.0 for Backups and Disaster Recovery.
Upcoming deprecation of GitHub Enterprise 2.13
GitHub Enterprise 2.13 will be deprecated as of March 27, 2019. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.
Upcoming deprecation of GitHub Services
Starting with GitHub Enterprise 2.17.0, support for GitHub Services will be deprecated and administrators will not be able to install or configure new GitHub Services. Existing GitHub Services from a previous version of GitHub Enterprise will continue to function but GitHub Enterprise will not be providing any security or bug fixes to the GitHub Services functionality. At this time, there will be no changes to the existing functionality, but a warning banner will be displayed with the deprecation announcement blog post. Administrators can see which repositories are using GitHub Services with
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
- Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
- Stricter REST API validation has been prematurely enabled. As a result, API requests that previously succeeded may be rejected with a
422 Unprocessable Entity response. (updated 2019-02-01)
The GitHub Team