GitHub

Link Pull Requests to issues: move the state and attach the PR automatically.

Open the PR and the task moves by itself. If the branch carries the task's identifier, opening the pull request on GitHub or Bitbucket attaches it to the task and moves it to in progress; merging it closes the task. Without touching the board. Watch in the feed →

The GitHub integration connects your repositories’ activity to Hilbana issues through a GitHub App.

What it is

Connected in Settings → GitHub (admins only): you install the GitHub App on your organization or account and they’re linked. The page shows the installation and its repositories.

What it’s for

When you work a Pull Request whose branch contains an issue’s identifier (for example drapps-142-... → issue DRAPPS-142), Hilbana:

Attaches the PR to the issue (number, link, branch and status).
Moves the issue’s state: when the PR is opened or reopened, to a started state; when it’s merged, to a completed state.

How to use it

In Settings → GitHub, click Connect and install the app on GitHub.
Name your branches including the issue’s identifier.
Open and merge PRs as usual: the issue updates itself.

Turning it off

If your team doesn’t work with GitHub, an admin can turn it off in Settings → General, with the “Use the Git integration (GitHub and Bitbucket)” switch (on by default). That hides the Git section on tasks, the GitHub and Bitbucket entries in Settings and the PR triggers in automations, and a milestone summary is then written from the tasks completed instead of the code changes.

It’s a workspace setting, not a personal preference: an admin changes it and everyone sees it.

Details

The connection is multi-installation: each event resolves to the right workspace, so the same GitHub App serves several customers without mixing them up.
Disconnecting removes the link in Hilbana (it doesn’t uninstall the app on GitHub).
The transition only happens if the issue’s team has a state in that category.

Related: Bitbucket · Issues · Workflow states.