Skip to content
BOSS*

Keep code review connected to the project it belongs to.

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

A closer look at GitHub integration

Illustrative records
BOSS*One connected workspace
Aqtos
OFFICEWORKPEOPLEMONEYTECH
TECH / GitHub integration

Code review in project context

Example workspace
GitHubplanet-express / webConnected to Website launch
Code review in project context
Pull requestProjectReviewerStatus
#42 · Fix the enquiry formPlanet ExpressRiley TorresReview requested
#43 · Update the launch pagePlanet ExpressLeo RainerReview requested
Repositoryplanet-express/web
BOSS* projectWebsite launch
Review ownerRiley
Aqtos
OFFICEWORKPEOPLEMONEYTECH
TECH / GitHub integration

Code review in project context

Example workspace
GitHub integrationDetails

Fix the enquiry form

GitHub · Pull request #42

Repository
planet-express/web
Project
Website launch
Reviewer
Riley Torres

The repository mapping and person mapping determine where the review work belongs.

Map repositories to BOSS* projects and GitHub accounts to your colleagues.Interactive illustration of BOSS*

GitHub integration in your working day

Give the reviewer the context beyond the pull request.

The code lives in GitHub. The delivery work lives with the project, where your team can see what needs review and who is responsible.

01

Connect the repository

Authorize the GitHub account with the repository access your workflow needs.

02

Map the project

Pair the repository with the BOSS* project that owns the work.

03

Match the people

Connect GitHub identities with Aqtos users so review work reaches the right colleague.

Get the connection working

Start with one workflow your team needs.

Set up the connection, check the result and make the handoff part of your routine.

Talk through your workflow
  1. Authorize GitHub

    Open TECH → Integrations → GitHub → Configure and review the requested access.

  2. Map repositories and people

    Save the project pairing and the corresponding user mappings.

  3. Check a review

    Use a small pull-request example and confirm the destination project and reviewer.

See how it fits your team

Bring your real workflow to a demo.

We’ll walk through the details with you, from the first record to the next action.

Book a personal demo

A few useful details

Questions about github integration

Explore the guides
Why can’t I see a repository?

Check the connected GitHub account’s access and any organization approval requirements for the OAuth app.

Why did review work reach the wrong person?

Check the GitHub-to-Aqtos person mapping and confirm that the repository is paired with the intended project.

Does this import all historical GitHub issues?

Repository authorization is not a full historical issue migration. Confirm the events and records you need with Aqtos.

Does BOSS* replace GitHub?

No. Keep repositories and development in GitHub, with relevant review work connected to the BOSS* project.

See how BOSS* fits
your working day.

We’ll use your email to arrange your demo. Privacy policy