Connect the repository
Authorize the GitHub account with the repository access your workflow needs.
Map repositories to BOSS* projects and GitHub accounts to your colleagues. Give review work a place alongside the other tasks needed to ship.
Explore BOSS* pricing| Pull request | Project | Reviewer | Status |
|---|---|---|---|
| #42 · Fix the enquiry form | Review requested | ||
| #43 · Update the launch page | Review requested |
GitHub · Pull request #42
The repository mapping and person mapping determine where the review work belongs.
GitHub integration in your working day
The code lives in GitHub. The delivery work lives with the project, where your team can see what needs review and who is responsible.
Authorize the GitHub account with the repository access your workflow needs.
Pair the repository with the BOSS* project that owns the work.
Connect GitHub identities with Aqtos users so review work reaches the right colleague.
Get the connection working
Set up the connection, check the result and make the handoff part of your routine.
Talk through your workflowOpen TECH → Integrations → GitHub → Configure and review the requested access.
Save the project pairing and the corresponding user mappings.
Use a small pull-request example and confirm the destination project and reviewer.
See how it fits your team
We’ll walk through the details with you, from the first record to the next action.
Check the connected GitHub account’s access and any organization approval requirements for the OAuth app.
Check the GitHub-to-Aqtos person mapping and confirm that the repository is paired with the intended project.
Repository authorization is not a full historical issue migration. Confirm the events and records you need with Aqtos.
No. Keep repositories and development in GitHub, with relevant review work connected to the BOSS* project.
fits