Skip to main content

Connect a repository

ACE Dev needs access to your code. This has two parts: connecting a GitHub account, then connecting a specific repository from it. Both are required.

Step 1: Connect your GitHub account​

  1. In your project, go to Integrations → Repositories.
  2. Connect GitHub, either by authorizing your account directly or with a personal access token.

New projects start empty

A fresh project has no connected accounts or repositories yet.

Connect with a personal access token​

Create a fine-grained token on GitHub, then paste it into ACE Dev.

On GitHub:

  1. Click your profile picture (top right), then Settings.
  2. In the left menu, scroll to the bottom and click Developer settings.
  3. Open Personal access tokens → Fine-grained tokens, then click Generate new token.
  4. Enter a token name. In Resource owner, pick the organization.
  5. Select Only select repositories and pick the repositories ACE Dev will use.
  6. Click Add permissions and add the seven permissions below.
  7. Click Generate token, then copy it now. GitHub shows it only once.
PermissionAccess
MetadataRead
ContentsRead and write
Pull requestsRead and write
IssuesRead and write
ActionsRead
WebhooksRead and write
WorkflowsWrite

In ACE Dev: go to Repositories → GitHub, click Use a token, and paste the token.

Why ACE Dev asks for each permission
PermissionWhat ACE Dev uses it for
Metadata (read)Used when you connect. ACE Dev lists the repositories in the account so you can choose which ones enter the project. Covers name, visibility, and main branch. No access to code.
Contents (read, write)Read builds the project knowledge base. ACE Dev reads your repositories to produce and keep current its own documentation of how your system is structured, so every review can see what a change breaks elsewhere. Write is the delivery. From an approved card, ACE Dev creates its own working branch and commits the change there. Commits go to that branch, never to your main branch. Without write, ACE Dev can analyze and recommend, but never deliver.
Pull requests (read, write)Read is the code review: the proposed change, affected files, commit history, and existing discussion, assessed for correctness, security, tests, performance, and impact. Write opens the pull request that carries a delivery, publishes the review where your team can see it, and records the approval once a person authorizes it in ACE Dev. The decision is always a person's.
Issues (read, write)Read checks what is open and whether something was already reported before proposing it again. Write opens or comments on an issue when you ask. It is not used to reorganize or clean up your backlog.
Actions (read)Gives ACE Dev visibility of your build, test, and deploy pipelines: which ran, pass or fail, duration, and the error log on failure. This lets it report deployment health and explain why something broke. Read only: ACE Dev cannot start, cancel, or alter a pipeline.
Webhooks (read, write)Lets ACE Dev react when something happens, instead of repeatedly querying your account, which is slower and wastes rate limit. You choose which notifications each repository sends. Write installs them when you connect a repository and removes them when you disconnect, so turning ACE Dev off leaves no configuration behind.
Workflows (write)GitHub protects the files that define build and deploy pipelines with a separate authorization. Needed only when a task asks ACE Dev to fix or adjust a pipeline. If declined, only that class of task fails. Everything else is unaffected.

Step 2: Connect a repository​

  1. In Integrations → Repositories, choose to connect a repository from your account.
  2. Search by name or wait for the list to load, then select the repository (for Trakk, the Trakk repo).
  3. Choose the branch to target (for example, main).
  4. Enable automatic PR analysis if you want every pull request analyzed.
  5. Validate, then confirm and add the repository.

The repository now appears under Repositories.

Working with multiple repositories​

A product split across several repositories (front end, back end, database) can connect each one here. ACE Dev maps them together as one system and knows which repository to change for a given request.

tip

Connect all of a product's repositories before you map, so ACE Dev learns how they connect.

Next steps​