The Precedent handbook
Repositories
A repository is a git repository recorded in your workspace. It follows Areas, and its assistants and pull request check use their decisions.
What a repository follows
A repository follows one to three Areas for all its files. It can also map folders to other Areas: for example, acme-robotics/fleet-api follows Platform, and its services/inspection/** folder follows Inspection. Its assistants and the pull request check use the decided decisions of every Area it follows.
A repository also records its new decisions in one Area, shown as Records in. The drafts its assistants propose are filed there.
Following an Area grants no access to it. A repository holds no decisions, approval rule or members of its own, so people still see only the decisions in Areas they can see.
Add a repository
On Repositories, choose Add repositories. An Area's page offers the same button, with that Area already ticked. To add one by name, enter the repository's owner and name on GitHub, such as acme-robotics/fleet-api, or paste its URL. Under Follows, tick up to three Areas, and under Records in, choose the Area where its assistants propose new decisions. The list offers only the Areas you may add it to. After adding, the repository's page links to setting up the pull request check.
With a GitHub connection, choose Add repositories, sign in with GitHub, and tick up to 50 repositories from the list. Precedent lists only repositories that both it and your GitHub account can see. Then choose the Areas they follow. A repository that is not listed, for example acme-robotics/firmware-tools in an organisation that has not given Precedent access to it, can still be added by typing its name.
An assistant can do the same. Connect your assistant, open the repository and ask: “Set up Precedent for this repository.” The assistant asks which Areas the repository should follow and where to record its decisions, then adds it to your workspace. If you are the only person in the workspace and it has at most one Area, your assistant adds the repository and records its decisions in that Area, or in a new one named after the repository, once you accept.
Connect GitHub
A workspace administrator connects GitHub under Settings → Integrations: choose Connect a GitHub account, sign in with GitHub, and choose an organisation or personal account where Precedent is installed. A workspace can hold up to 20 GitHub connections. Precedent sees repository names and settings on that account, never code.
Removing a connection keeps every repository already added, with its Areas and history.
Kept current from GitHub
When a repository is renamed, archived, deleted, or made public or private on GitHub, moved into a GitHub account connected to the workspace, or Precedent loses access to it, Precedent updates the repository and adds a line to its History. A repository Precedent can no longer see shows Access removed on GitHub and keeps its Areas, decisions and pull request check. Precedent learns of these changes only for GitHub accounts connected to the workspace.
The repository page
Repositories in the sidebar lists the repositories you can see, with the Areas each follows and when the pull request check last ran. You can see a repository that follows or records in an Area you can see, and one you added. Workspace administrators see every repository.
A repository's page shows the Areas it follows, where it records decisions and when the pull request check last ran. Below them are the decisions in force from the Areas it follows and the Areas its folders follow, grouped as Expired, Reviews due and Decided, with each decision listed once. A decision from a folder's Area applies only to files in that folder. Folders lists the folder patterns mapped to Areas, and History lists each change to the repository, newest first.
An Area you cannot see is counted, never named: the page reads, for example, “Follows Platform and 1 Area you cannot see”. Not checked yet means no pull request check has run for the repository. If it stays that way, check that its name matches the repository on GitHub. A repository chosen from a GitHub connection is proved when it is added, so its name already matches GitHub. It still shows Not checked yet until its first pull request check runs.
Beside the Areas it follows and where it records are the controls to add or remove an Area and to change where it records, shown only for the changes you may make.
Who can change it
Anyone who is not a Viewer can add a repository. To make it follow an Area, you need Member access or higher to that Area. A restricted Area needs its Area administrator or a workspace administrator, because the repository's readers then see the titles of its decisions.
Changing where a repository records its decisions needs Member access or higher to the new Area. Removing an Area from a repository needs that Area's administrator or a workspace administrator, and a repository always follows at least one Area.
A workspace administrator can remove a repository. The person who added it can also remove it, until a pull request check has seen it. Only a workspace administrator confirms a new owner after the repository moves to another owner on GitHub.
An assistant can add a repository but cannot change one. Viewers, and everyone in a read-only workspace, see repositories and change nothing. Following an Area grants nothing either way: people still see only the decisions in Areas they can see.