Importing and managing repositories
This is the repository list below the provider cards on Integrations → Repositories. It shows the workspace's connected repositories, scoped to whichever project you have selected.
Connect Repository (the import wizard)
Click Connect Repository (or Connect your first repository on an empty list) to open a 5-step modal:
- Choose a project: repositories are connected to a project and worked on by its agents. Defaults to the currently active project if you are allowed to manage it, otherwise the workspace's default project, otherwise the first manageable one.
- Choose an account: lists the GitHub and GitLab accounts already assigned to that project. If none are assigned, it tells you: "No GitHub or GitLab account is assigned to this project. Assign one on the Integrations page (per-account → 'Select projects'), then come back." (See Connecting a provider account.)
- Configure repository: pick a repo either by Select (a searchable dropdown of the account's repos, marking private ones) or Paste link (a GitHub or GitLab URL, or a bare
owner/name), then pick a branch (also searchable, and it accepts free text so a branch outside the fetched page still works). You can stage several repositories here before moving on, and each staged item is listed with a remove button. - Validate repository: before a staged repo can be confirmed, ACE checks it against the provider: read access, write access, webhook, and CI/CD (Actions) permissions, shown as a per-check list with pass/fail icons and any error detail. Only a passing validation unlocks Confirm add repository; a failure lets you Edit (back to step 3) or Retry validation.
- Review & connect: the full staged list, each removable, with Add another repo to go back to step 3.
Connect <N> repositoriessubmits the batch; any that fail come back as an error listing which repo and why, while the rest still succeed.
The repository list
Each repository shows as a card with:
- Name, a status badge (Ready, Indexing, or Error), the project it belongs to, and its default branch (the branch selected when it was added).
Provider events: <state>: the health of the webhook and event subscription behind it (Off, Provisioning…, Reconciling…, Updating…, Active, Needs attention, Turning off…, Removed).- If it has an active chat session, a Continue where you left off box to resume that conversation directly (requires
chat:access; without it, a plain note explains why the box is inert). - Document count and a relative "Last updated" timestamp.
The ⋯ menu on a card offers:
Reconnect <provider>: re-runs OAuth for the account behind this repo (only if you also haveorg:integrations:manage; see permissions).- Move to project…: reassign the repository to a different project you can manage.
- Disconnect: with a confirmation explaining "ACE removes the provider webhook first, then removes the repository and its issues." While cleanup is in progress the card shows "Disconnecting" and a note that it will disappear once the webhook is removed; if cleanup itself fails, the card offers Retry disconnect (or, if the account needs re-authorization first,
Reconnect <provider>followed by retrying).
When sync breaks
If one or more repositories show an Error status, a banner above the list reports how many failed and explains: "The connected account may have lost access or its token expired. Reconnect to restore access," with a Reconnect <provider> button per affected provider. Reconnecting is account-level: fixing one account revives every repository that shares it, and also refreshes the Pull Requests list.
Repair provider events
Repair provider events (next to Connect Repository, only when a project is selected) compares ACE's webhook and event delivery against the provider for every repository in the current project and repairs any drift. It reports back, for example "Provider event repair queued: 3/4 repositories. 1 skipped" (skipped repos have no supported events, which is benign), or flags any that errored outright as needing a log check.
How do I filter the list?
A text filter above the list matches repository name or full owner/name against your search, showing "N of M repositories connected" while filtered.
Related
- Connecting a provider account: required before you can import anything.
- Knowledge: Discovery needs at least one connected repository before it can map your code.
- Pull Requests and Deployments: both are populated from the repositories connected here.