Connect GitHub and link issues to requests and roadmap items
Install the Releaseo GitHub App, connect repositories, link issues to feature requests and roadmap items, and tune per-repository automation.
The GitHub integration closes the loop between customer requests and your engineering work. A feature request becomes a GitHub issue, closing the issue stages an announcement, and publishing your changelog tells the people who asked.
Connect GitHub
Open Integrations in the sidebar and choose GitHub.
Under the GitHub App banner, select Install the GitHub App.
On GitHub, choose Only select repositories and pick the ones you want. Releaseo never needs access to code you have not connected.
If you install into an organization and an admin has to approve it, Releaseo tells you that approval is pending. The installation appears on the page once they approve.
Back in Releaseo, select Add repository under Connected repositories.
In Connect a repository, pick the Repository. Repositories already connected show an Added chip. If you see "No repositories are visible to this installation", grant access on GitHub and reopen the dialog.
Under Which side writes releases?, choose a direction (see below), then select Connect.
You need permission to manage integrations to install the app and connect repositories. Your plan may also limit how many repositories you can connect.
If a repository row shows Finishing setup, Releaseo is still wiring it up. Give it a moment.
Choose a release direction
Each repository uses one direction at a time, so a changelog post and a GitHub release never overwrite each other:
Releaseo writes the announcement: publishing a changelog post creates a draft GitHub release on the matching tag. Nothing is tagged or published on GitHub without a person doing it.
GitHub is where releases happen: publishing a GitHub release creates a draft changelog post in Releaseo, ready to review.
Issue linking works in both modes. Each row shows the direction as Releaseo → GitHub or GitHub → Releaseo.
Link an issue to a feature request or roadmap item
Once at least one repository is connected and enabled, a GitHub section appears on feature requests and, for roadmap items, on the Linked requests tab of the item's detail drawer. If you have no enabled GitHub connection, the section is hidden.
Open the feature request or roadmap item.
In the GitHub section, select Attach issue.
In Attach a GitHub issue, pick the Repository.
Choose one of two options:
Open a new issue: creates it from this item, copying the title and description. Select Create issue.
Link an existing issue or PR: enter the Issue or PR number, then select Link issue.
A new issue takes a moment. You will see "Opening the issue on GitHub. It will appear here in a moment."
Each link shows its number and a status chip:
Chip | Meaning |
|---|---|
Opening… | The issue is still being created. |
Open | The issue is open. |
Closed | The issue was closed as completed. |
Closed — not planned | The issue was closed and the work is not coming. |
Linked | You linked it before GitHub reported its state. |
Pull requests can be linked too. They show Open PR, Merged, or Closed — not merged, and nothing is automated from them.
Use the open icon to view the issue on GitHub. Use Detach to unlink it. The issue stays on GitHub, and Releaseo just stops following it.
Automate per repository
On the GitHub page, select Settings on a repository row to open its settings.
Release direction: switching it shows a warning. The old direction stops when you save, and existing posts and releases are left as they are. In "Releaseo writes the announcement" mode you can also set a Tag prefix and a Release branch. Leave the branch empty to use the repository default.
Issues from feature requests, Create the issue: choose Only when I click the button, Automatically, when a request is approved, or Automatically, when an item enters a column. Only one repository per project can open issues automatically.
Issues onto the roadmap: turn on Import labelled issues as roadmap items, set the Label, and choose where imports land in Imports land in. Imported items are internal until you make them public.
When an issue closes: Move the roadmap item to Ready to announce. A closed issue means engineering finished, not that customers were told. Nothing is marked released until you publish the changelog.
When you publish: optionally move staged roadmap items to Released, mark linked feature requests as done, and email the people who voted. Voter emails are sent from your own SMTP, so connect it first.
Use Test in the row or its actions menu to check a repository. Disconnect stops syncing but keeps existing links, so reconnecting later does not re-import past releases.
Troubleshooting
The installation is suspended or removed. Banners on the page explain that nothing syncs until it is resumed or reconnected on GitHub. Your linked issues and releases are preserved.
I can't turn on automatic issue creation. Another repository in the project already opens issues automatically. The error names it.
The Attach issue button is missing. You need permission to manage the item, and the project needs an enabled GitHub repository.
Was this article helpful?
Still stuck? Contact us and mention this article.