Pull requests on the card
A pull request is a request to merge a set of code changes into the main code. GitHub is where many developers keep that code. devBoard links each pull request to the task it is for. It can also move the card when the pull request opens, merges or closes. It is for developers who want the board to keep up without updating it by hand.
How it works
A webhook is a message one service sends to another when something happens. Each workspace has one webhook address. You add it to your GitHub repos. From then on, GitHub tells devBoard about each pull request.
devBoard looks for task keys, like APP-42, in three places: the title, the body and the branch name. A branch is a separate line of work in git. Case does not matter, so a branch called app-42-fix-login counts. Each key it finds gets a link, so one pull request can link several tasks.
The task then lists the pull request by repo and number, with its state: Open, Merged or Closed. Tap it to copy its link.
An admin picks where the card goes at three moments. Out of the box it looks like this:
| When the pull request | The card moves to |
|---|---|
| Opens | In progress |
| Merges | Done |
| Closes without merging | Nowhere, it stays put |
Each choice is a group, not one column. The card goes to the first column in that group, on its own project's board. An opening pull request only moves cards that have not started. A merge or close leaves cards alone if they are already done or cancelled.
Each task also shows a branch name to copy, made from its key and title. MCP is the open standard that lets an AI assistant use other tools. Over MCP, start_work hands you the same branch name and starts your timer. A pull request from that branch links itself.
An example: Luka, Mira and Ivan
Luka, Mira and Ivan are a three-person studio shipping a mobile app. Luka picks up APP-57, "Fix the login crash". He copies the branch name from the task, app-57-fix-the-login-crash, and starts coding.
When he opens a pull request, the card moves from To do to In progress. Mira reviews the code and merges it. The card moves to Done, and the task shows the pull request as Merged. Nobody touched the board.
What it does not do
- GitHub only. No GitLab, no Bitbucket, and no Slack or other links.
- Pull requests only. Commits, issues and review comments are not read.
- It does not open or merge pull requests for you.
- No build status on the card. CI is a service that runs your tests on each change, and devBoard does not show its results.
- A card moved by GitHub shows the workspace owner as the one who moved it. GitHub is not a member, so the owner stands in.
Set it up
In the Mac app, go to Settings, then Developer. Under Pull requests, an admin copies the webhook address and sets a webhook secret. Then pick where a card goes when a pull request opens, merges or closes. In GitHub, add a webhook with that address and secret. Choose JSON as the content type, and pull request events. The guide on how to link GitHub pull requests has every click. Or see all devBoard features.
Questions people ask
Do I have to paste a link into the task?
No. Put the key, like APP-42, in the pull request title, body or branch name. devBoard finds it and adds the link.
Does it work with GitLab or Bitbucket?
No. It works with GitHub only, and only with pull requests.
Can one pull request close two tasks?
Yes. Put both keys in it, like APP-3 and APP-4. Both tasks get the link, and both cards move.
Free while in early access; paid plans will be one plain number, posted here first.
Download on the App Store Get it on Google Play Connect your AI assistant