GITHUBGuide

Link branches and PRs to issues

Name the branch with the issue's code — or reference the issue in the PR — and Forge shows branches and PRs in the issue's Desenvolvimento (Development) panel, and can move the status when the PR merges.

Create the branch with the right name

  1. 1

    Open the issue's full page.

    The Desenvolvimento (Development) panel shows the suggested branch name. It doesn't appear in the overlay panel — use Abrir página completa (Open full page).

  2. 2

    Copy it with `Copiar nome da branch` (Copy branch name) or `Copiar comando git checkout` (Copy git checkout command).

    The suggestion follows the iss-N-... pattern, with the issue's number — that's what links the branch to the issue.

  3. 3

    Create the branch and publish it to GitHub.

    bash
    git checkout -b iss-42-corrigir-exportacao-csv
    result
    The branch appears on the issue, under “Branch já criada” (Branch already created), with a link to GitHub.

Link the PR

A PR opened from an iss-N-... branch is born linked. Without a branch in the pattern, write closes #N in the PR description — N is the issue's number. The panel shows each PR with the state Aberto (Open), Mesclado (Merged), or Fechado (Closed), with a link to GitHub.

While nothing references the issue, the panel shows “Nenhum PR vinculado” (No linked PR) with the linking instructions — follow the steps above.

Move the issue on merge

With the Fechar issues ao mesclar PR (Close issues on PR merge) option turned on in the integration, merging a linked PR moves the issue automatically to the status the team configured — for example, Concluído (Completed) or Pronto p/ deploy (Ready to deploy).

The branch helper works without GitHub connected

The copy-name and copy-command buttons appear on every issue. The PR list and branch detection, though, depend on the GitHub integration being installed.

Next