For the first time, your team can connect to the power of the open source community—and find lots of ways to get more work done—with our latest Enterprise release.
Ready to start using these new tools? Upgrade your instance:
Now, if you have GitHub Business Cloud in addition to your Enterprise instance, you can tap into everything you love about open source from behind your firewall. Find public content and collaborate with the entire GitHub community without sacrificing security.
The Checks API helps integrators build sophisticated tools for continuous integration, linting, and acceptance testing on GitHub. Previously, integrators could report success or failure of a build and include a link to more information using our Statuses API. With the new Checks API, they can specify more status information during builds and collect richer data, providing a more integrated experience for developers.
Project maintainers can now organize contributions and reduce noise for projects that have lots of collaborators with multiple issue templates and an improved setup process.
When reviewing code, a diff with a number of white space changes can distract from the changes that matter. Now it’s easier to understand code updates from white space changes with an improved diff view. Change your view to automatically filter it out by clicking Diff settings.
As projects grow, you may want additional reviews for your team’s code changes. With the new multiple reviewer requirement, you can set how many reviewers are required for every pull request on a protected branch—so your organization’s important projects are protected from unwanted changes.
Now you can create a support ticket directly from Enterprise and send diagnostic information to get help faster. We’ve also created a new command—
ghe-support-upload—to directly upload your support tickets with the output of commands.
Enterprise 2.14 adjusts the default threshold for developers who are considered dormant from 30 to 90 days, so developers can retain access longer—and admins can now configure the threshold to fit their team.
You can now opt in to configure anonymous git access to public repositories when your Enterprise environment is in private mode. This helps continuous integration tools and build machines seamlessly access code for testing or deploy pipelines—and makes it easier for them to distribute Go or Swift projects that use
git for submodules.
To see the full list of updates, check out our release notes.
Our latest GitHub Enterprise release has arrived with new ways for teams to collaborate, manage permissions, build custom tools, and more. Here’s an overview of what you’ll get when you upgrade to 2.13.
Team discussions give your team a dedicated home for conversations that aren’t related to code changes—so they’re easy to find when you need them without cluttering issues and pull requests.
With commit co-authors, your team can see who has contributed to every commit, regardless of how many contributors there are and make sure every author gets attribution in the pull request and in their contribution graph.
Built-in authentication with external providers
It’s easier than ever to make sure the right developers, contractors, and machine users have access to your instance with built-in authentication providers. And having more than one authentication process means that you always have a fallback when an external adaptor goes down or is undergoing maintenance.
Extended pre-receive hooks
We’ve extended pre-receive hooks so policies can be configured when code is pushed to your instance. With Git push options
(--push-options), developers can transmit strings to the server for your pre-receive hooks.
Hotpatching for clustering
With hotpatching updates, you’ll now be able to roll out hotpatches for clustering without downtime.
Grafana in your Monitor Dashboard
Your Monitor Dashboard just got an upgrade of its own with the help of Grafana! Now you’ll be able to access more detailed performance graphs for your instance and have more control over how you analyze and share data in your organization.
GitHub Apps are fresh out of preview and fully available for teams using GitHub Enterprise 2.13. Now you can customize your workflow in just about any way you’d like with the help of GitHub APIs.
To learn more, check out our release notes or RSVP for one of our upcoming webcasts:
GitHub Enterprise 2.12 has arrived with new organization tools to help your team stay focused and do their best work. Get project board enhancements, global webhooks, repository archiving, and more by upgrading to our latest release.
Ready to upgrade? Download GitHub Enterprise 2.12
Project boards help you keep track of what’s happening with a group of tasks. Now, with automation events, you can let your project boards update the status of your tasks for you. Whether you or a teammate add a new card to a project, close an issue, or merge a pull request, your cards will automatically move between columns in real time.
If you rely on assistive technology or prefer using the keyboard to manage project boards, you can now use our new keyboard shortcuts to quickly navigate between cards and columns. Simple keystrokes allow you to move cards and columns anywhere on the board, commit changes, or review the keyboard shortcuts in more detail.
Project boards are a great way to organize tasks, but often, those tasks have external dependencies. With our new Enterprise release, you can use notes to add links to those dependencies. When 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, giving you more context.
Now you can configure webhooks for an entire enterprise instance instead of one repository or organization at a time. Admins will be notified about new users and organizations, deleted users and organizations, and membership changes.
You don’t have to delete repositories when they’re inactive. Now you can archive older projects to make them read-only to owners and contributors. While no one will be able to add new issues, pull requests, or comments, you’ll be clutter-free and still have access to the repositories if you decide to iterate on them later.
With Enterprise 2.12, you can also search for repositories by their license using license family names or queries like “license:mit” and “license:gpl-3.0”. License searching gives you another way to find projects that fit your licensing requirements or repos you’d like to work on. We’ve even added a license filter on the “Advanced Search” page to help you craft the exact query you need.
GitHub Enterprise now supports Let’s Encrypt, a public Certificate Authority (CA), which 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.
Download GitHub Enterprise 2.12 to start using these tools. You can also check out the release notes to see what else is new or enable update checks to automatically check for the latest GitHub Enterprise release.
Not using GitHub Enterprise yet? Request a 45-day free trial
Continuous Integration (CI) tools help you stick to your team’s quality standards by running tests every time you push a new commit and reporting the results to a pull request. Combined with continuous delivery (CD) tools, you can also test your code on multiple configurations, run additional performance tests, and automate every step until production.
There are several CI and CD tools that integrate with GitHub, some of which you can install in a few clicks from GitHub Marketplace. With so many options, you can pick the best tool for the job—even if it’s not the one that comes pre-integrated with your system.
The tools that will work best for you depends on many factors, including:
Of course, it isn’t possible to optimize your CI tool for all of these scenarios. The people who build them have to choose which use cases to serve best—and when to prioritize complexity over simplicity. For example, if you like to test small applications written in a particular programming language for one platform, you won’t need the complexity of a tool that tests embedded software controllers on dozens of platforms with a broad mix of programming languages and frameworks.
If you need a little inspiration for which CI tool might work best, take a look at popular GitHub projects. Many show the status of their integrated CI/CD tools as badges in their README.md. We’ve also analyzed the use of CI tools across more than 50 million repositories in the GitHub community, and found a lot of variety. The following diagram shows the relative percentage of the top 10 CI tools used with GitHub.com, based on the most used commit status contexts used within our pull requests.
Our analysis also showed that many teams use more than one CI tool in their projects, allowing them to emphasize what each tool does best.
If you’d like to check them out, here are the top 10 tools teams use:
It’s tempting to just pick the default, pre-integrated tool without taking the time to research and choose the best one for the job, but there are plenty of excellent choices built for your specific use cases. And if you change your mind later, no problem. When you choose the best tool for a specific situation, you’re guaranteeing tailored performance and the freedom of interchangability when it no longer fits.
Ready to see how CI tools can fit into your workflow?
Enhance performance in high availability environments, define more granular permissions, and seamlessly review code with GitHub Enterprise 2.11. Our latest release brings together some of the most-requested features to make your team’s development process smoother and more efficient.
Ready to upgrade? Download GitHub Enterprise 2.11
Geo-replication is now out of early access and available in Enterprise 2.11. Geographically distributed data centers use multiple replicas, so requests are always sent to the closest server and fulfilled faster than ever before.
Hotpatching is also out of early access and available in GitHub Enterprise 2.11. Now, you’ll almost always be able to upgrade to a newer patch release with zero downtime—no need to sweat about last minute security fixes.
Whether you’re working on a project within your team or across departments, nested teams keep information clearly organized. With Enterprise 2.11, you can make sure the right people have access to the right code and reduce noise as contributors grow. Child teams inherit their parent’s access permissions, so repository permissions and mentioning among nested teams work from top to bottom, improving the flow of communication. For example: If your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access.
Great reviews can take a village. With team reviews, you can ask an entire team to look at your pull request with one mention. Just tag the team in the “Reviewers” section of your pull request for better reviews from more teammates in less time.
You can now define exactly which people and teams always need to review projects with code owners. Select code owners, and they’ll automatically be requested for review when a pull request touches the files they own. There’s also a protected branch option, which requires code owners to leave a review before anyone can merge a pull request to the branch. Never worry about mistaken merges going unnoticed again.
Download GitHub Enterprise 2.11 to start using these features today. You can also check out our release notes to learn more, and enable update checks to automatically check when the next GitHub Enterprise release is available.
Want to try GitHub Enterprise? Request a free 45-day trial