Code and repositories / Repository settings
Write down who knows what
New issues and pull requests come in, and a contributor does not know who knows the git engine, or who to ask about CI. The Experts section of the settings writes it down: each maintainer adds what they know and the paths that they care about.
3 min read
You need the triage role or more on the repository to add an entry. Everyone who can read the repository sees the list.
1. Open Experts
Open the repository, then Settings, then Experts under People.
2. Say what you know
- Click Add my entry. If you have an entry, the button is Edit my entry.
- In What you know, say what you know, in up to 1000 characters. For example: "the git engine and its pack files".
3. Add your paths
In Paths, type the paths that you care about, one per line, up to 20 paths. A path is a glob:
*matches any characters, but not/. Sodocs/*.mdmatchesdocs/cli.md, but notdocs/ci/reference.md.**matches any number of folders. Sopackages/git/**matches each file underpackages/git.- A line that starts with
!leaves paths out. - If two lines match a path, the later line decides. So put a
!line after the line that it narrows.
This entry takes the git engine, but not its tests:
packages/git/**
!packages/git/test/**
4. Save
Click Save. Your entry shows in the list, with what you know and your paths.
Done
- The Experts section of Settings shows who knows which part of the repository, to everyone who can read it.
- When the Assign agent is on, it reads the active entries and the active code owners. For each new issue and pull request with no assignee, it assigns up to 2 people, each with a note that says why. See Issue agents.
Find who to ask
- Open the repository, then Settings, then Experts under People.
- Find the paths of the code that your question is about.
- Ask the person of that entry. Each entry shows what the person knows, under their name.
If the repository has a CODEOWNERS file, the Code owners section under the entries shows its rules. Find the last rule whose pattern matches your files, and ask its owners. See Ask code owners to review with CODEOWNERS.
Note
An Inactive badge means that the person no longer has the triage role or more. Their entry stays, and the Assign agent skips it. When the person gets the role back, the entry is active again.
Delete an entry
To delete your entry, click Delete on your row, then click Delete entry. A repository admin can edit or delete the entry of each person.
Set your entry with src
src expert set --about "the git engine and its pack files" \
--path 'packages/git/**' --path '!packages/git/test/**'
- Give
--pathonce for each path. The command replaces your whole entry, so give all your paths each time. src expert listshows the entries. Add--json username,pathsfor JSON.src expert deletedeletes your entry.- Outside a clone of the repository, add
-R OWNER/REPO.
With no username, a command acts on your own entry. A repository admin can give a username, for example src expert set ana --about "the CI images". The person must have the triage role or more.
Set entries with REST or MCP
src api -X PUT repos/<owner>/<repo>/experts/ana \
--input - <<'EOF'
{ "about": "the git engine and its pack files", "paths": ["packages/git/**", "!packages/git/test/**"] }
GET .../expertslists the entries.activeisfalsewhen the person no longer has the triage role or more.DELETE .../experts/{username}deletes one entry.- The MCP tools are
list_experts,set_expertanddelete_expert. Leave outusernameto change your own entry.