GitHub has launched the most recent model of GitHub Enterprise Server, which is a self-hosted model of GitHub.
“With this model, prospects can select the best way to greatest scale their safety technique, achieve extra management over deployments, and a lot extra,” GitHub wrote in a weblog put up.
Key highlights of GitHub Enterprise Server 3.12 embrace the flexibility to limit deployments to sure tag patterns, organization-wide repository rulesets that may be utilized to sure workflows, merge queues, and Dependabot alert guidelines.
Tag patterns permit customers to be extra particular about what will get deployed into manufacturing by way of GitHub Actions, offering a further layer of safety and management. For example, a developer may specify that solely issues with the “Releases/” tag be deployed into manufacturing.
One other safety enchancment is that customers can now outline and implement rulesets throughout a number of repositories. This replaces the legacy required workloads characteristic, and any workflows that have been utilizing these have been routinely migrated to rulesets.
GitHub Enterprise Server 3.12 additionally makes it simpler to automate department administration by way of the brand new merge queue characteristic. Marge queue routinely checks {that a} PR is suitable with different modifications and alerts builders if one thing is mistaken. It does this by creating a short lived department that comprises the most recent modifications from the bottom department, modifications from different PRs within the queue, and the modifications within the present PR.
This launch additionally provides user-configured alert guidelines in Dependabot, which is a device that updates dependencies in tasks.
“With Dependabot, you’ll be able to proactively handle safety alerts to make sure high-priority gadgets are surfaced. With user-configured alert guidelines, now you can tailor your safety technique to your particular threat tolerance and contextual wants, streamlining alert triage and remediation processes,” GitHub wrote.
Different options embrace secret scanning for non-provider patterns (beta), help for all CodeQL languages, GitHub Undertaking templates on the organizational stage, improved world navigation, and the flexibility to focus on textual content in markdown information.
