Integration · Included
GitHub integration: pull requests next to tasks
The task key in a branch name or a pull request title is all it takes. The task shows the review and check status, and can close itself once merged.
Developers don't click anything in assign2me. Your code stays on GitHub — we store only names, numbers, titles and states.
Step-by-step setup
Three steps, two people
- An administrator connects GitHub. In Integrations they install the assign2me app in a GitHub account or organization and pick all repositories or only some. Changes to the list on GitHub show up in assign2me within a minute.
- The project owner pins repositories. They choose repositories for their project and decide on automations. One repository can be pinned to several projects.
- The team uses the task key. In a branch name, a pull request title or description, or a commit message. The link appears on the task within 60 seconds.
Naming convention
A branch with the task key, ready to copy
Every task has a key made of the project prefix and a number, e.g. A2M-142. “Copy branch name” on the task gives you a ready name, and a second button copies the whole git checkout command.
Branch
The task shows “in progress: branch a2m-142-…” and a history entry. Its section and owner don't change.
Pull request
The task shows the author, review state, reviewers and check results.
Commit
Letter case doesn't matter. One pull request can point to several tasks.
Closing references
Which link closes a task and which only informs
A task closes only when the last open pull request with a closing link is merged, and only on a merge into the default branch (or branches the owner adds, such as release/*). A task someone reopened by hand is not closed again by the same merge.
- A2M-142
A closing link: once merged, the task can close itself if the project owner turned that automation on.
- refs A2M-142
Informational only, as are “ref” and “related to”. A merge won't close the task.
Project automations
Off by default, each one separately
- When a pull request opens — move the task to a chosen section, e.g. “In review”.
- When it is merged — complete the task or move it to a chosen section.
- Every automated change goes into the history with the source “GitHub”, the repository and the PR number, and sends the same notifications as a manual change.
- A “Code” filter on the list and board: waiting for review, changes requested, failed checks, merged while the task is still open.
GitHub App permissions
Read-only
- Metadata: read
- Repository contents: read — branches and commits; we never store code
- Pull requests: read
- Checks and commit statuses: read
assign2me stores branch names and pull request numbers, titles and states. Never your code, diffs or review comments. Limit or revoke access in your GitHub settings.
Working with clients
Your client sees the task, not the repository.
Guests don't see a task's Code section, and code status never goes to a Slack channel. Only team members with access to the task see GitHub information.
Questions about the GitHub integration
Full guide in the documentation →We have a monorepo with several projects. Does it work?
Yes. Pin one repository to several projects; tasks are recognized by their key prefix (e.g. A2M-, WEB-). Automations change only tasks of the project the repository is pinned to.
A project uses many repositories.
Pin them all to the project. One task can have several branches and pull requests from different repositories.
We have several GitHub organizations.
An assign2me organization can have several app installations, e.g. one per GitHub organization. Each installation belongs to one assign2me organization.
What happens when we disconnect?
Credentials are deleted and new events are rejected within 60 seconds. Existing links stay on tasks with their last known state, marked as outdated.
Do private tasks close too?
No. Automations never touch private tasks.
Everything for one price
30 days free. Then €19 per month excl. VAT for a team of up to 5, each additional person +€3.50. Client guests: unlimited and free.