Quevell reads GitHub. A company installs the Quevell app on its account or organization, chooses the repositories, and its issues start showing branches, commits and pull requests.
Permissions
All four permissions are read-only:
| Permission | What for |
|---|---|
| Metadata | The list of repositories the installation can see |
| Contents | Branches and commits |
| Pull requests | Pull requests, their titles, authors and states |
| Checks | Check results for a pull request |
What Quevell stores
- The connection: the account, the installation ID, who connected it and when.
- The installation's repositories: the name and number of each.
- The links on issues: the kind (branch, commit, pull request), the number or name, the title, the author, the state, check results, the URL.
- The connection's journal: time, event type, repository, outcome, and the reason when an event was not used.
The body of a delivery is not kept: it is erased as soon as it has been read. The user token used to verify access to the installation is never stored.
Connecting
Administration, the Integrations tab, the "Connect GitHub" button. The "Edit company settings" permission.
GitHub then asks which account to install the app on and which repositories to show it, and sends you back. The connection belongs to the company you pressed the button in; one installation belongs to one company.
A project's repositories
Project settings, the Development section. The "Manage who can reach a project" permission.
A project chooses from what the company connected. Each chosen repository has a "Link by issue key" switch: with it on, a branch, a pull request or a commit that mentions an issue key of the project linked to that repository is shown on that issue; with it off, only links added by hand are shown.
Linking by issue key
The key is looked for in a branch name, in a pull request's title and in a commit message. The key has to belong to a project linked to that repository, or no link is made.
If a name contains something that looks like a key but the company has no such project (a branch called release-2026, say), no link is made and the journal says nothing about it.
The Development block
On an issue, the block shows branches, commits and pull requests. A pull request is shown by the word for its state: draft, open, changes requested, approved, merged, closed, and beside it the check results.
If GitHub hasn't reported a pull request's state yet (for example, it was linked manually), the block says so. The state appears after the next event or status check.
Linking and unlinking manually
Paste a pull request's URL into the block's field to link it. The repository has to be one the company connected.
Every link has an "Unlink" button, including the ones Quevell made by reading a key. The permission: "Edit issues". An unlinked item stays unlinked: events about that pull request or branch no longer attach to the issue, and neither do the commits of an unlinked branch. Linking it again by URL brings it back and lifts the restriction.
Board badges
A card on a board is badged when its issue has a pull request: an open one outranks a merged one, and a closed one is not badged at all.
Events for automation
Automation rules can trigger on: a branch created, a commit linked, a pull request opened, ready for review, approved, changes requested, merged, closed.
Refreshing the list of repositories
The connection's card, the "Refresh" button. The "Edit company settings" permission. Quevell asks GitHub which repositories the installation can see and updates the company's list to match: new repositories are added, removed ones are dropped.
If a repository a project uses would be dropped, Quevell asks first, naming the repositories and how many project links they have. Dropping them also removes the links on issues into those repositories.
Once a minute per connection at most.
Connection status
A connection's card says one of three things: receiving events, nothing received for more than a day, installation removed. Beside it, when statuses were last checked and how many pull requests were checked.
Disconnecting
The "Disconnect" button on the connection's card. Before it happens, Quevell says how many project links go and how many issues lose their GitHub links.
The repositories, the projects' links to them and the links on issues go with the connection. Both connecting and disconnecting are recorded in the company's audit trail.
If you see a message after returning from GitHub
"This link has expired". More than fifteen minutes have passed, or the app's settings changed. Open Administration, Integrations and press "Connect GitHub" again.
"This window can be closed". Saving an installation's settings on GitHub leads here. Nothing was changed here; connecting starts with the button in Administration.