Rules on every way into a repository
Branch rules, code owners and secret scanning apply to pushes, web commits and merges alike, and reads of your code can be recorded.
Branch rules
Protect a branch, or every branch with a prefix like release/*: require a pull request and approvals, and block force pushes and deletion. People on a bypass list can skip the pull request, never the blocks.
Code owners
A CODEOWNERS file, in GitHub's syntax, names who owns which paths. With code owner reviews on, each owned change needs an approval from one of its owners.
Secret scanning
Turn it on, and pushes, web commits and merges that carry credentials, such as cloud access keys, private keys and tokens, are refused. A finding that isn't a secret can be allowed for an hour, with a reason.
Restricted repositories
Keep a repository to the people, groups and machines on its list, at read, write or admin. Roles don't count there, and owners manage the list without reaching the code.
Who read what, and when
Read auditing
Record every clone and archive download, or every read, in your organisation's audit log.
Alerts for owners
Owners hear about new Git keys, access list changes and clones from a key, network or country not seen in 180 days.
Every exception recorded
Bypasses, allowed findings and access list changes all go to the audit log.
Kept apart
Each organisation's repositories are its own, so other organisations can't see or reach them.
See Git with your team's code
Tell us how your team builds and ships today, and we'll walk you through Git and Pipelines set up the same way.
- A pull request from review to merge, with its checks
- Moving repositories and workflows from GitHub
- Questions about plans for larger teams
We use what you send to reply to you, as our Privacy Policy describes.
The form opens your email app with the message ready; nothing reaches us until you send it there.
Ship your team's code from Git
Complete and Enterprise include it, with Pipelines, Cloud and the rest of your workplace.