Does this work with private repositories?

Yes. The GitHub app only accesses the repositories you explicitly grant during installation, public or private.

How does Planoda know which issue a PR belongs to?

It matches the issue identifier (like ENG-1234) found in the branch name, PR title, or PR body. You can include it in any of those.

Can I turn off automatic status changes?

Yes. Automation rules are per team and fully optional — you can keep linking on while leaving status transitions manual.

Is GitHub Enterprise Server supported?

The cloud GitHub.com integration is available now. GitHub Enterprise Server (self-hosted) support is not yet available.

Developer tools · Available now

GitHub integration.

Keep issues and code in lockstep. Reference an issue in a branch or pull request and Planoda links them, surfaces the PR on the issue, and moves status as the PR opens, merges, and deploys.

Get started — free Browse all integrations

GitHub integration in short

The GitHub integration connects GitHub with Planoda — available now.
Keep issues and code in lockstep. Reference an issue in a branch or pull request and Planoda links them, surfaces the PR on the issue, and moves status as the PR opens, merges, and deploys.
What you can do: Link a PR to an issue by including the issue identifier (e.g. ENG-1234) in the branch name, PR title, or description — no manual linking step. Automate status transitions: issues move to In Progress when a linked PR opens and to Done when it merges, following rules you configure per team.
Connect it from Settings → Integrations in a few steps — no code required.

What you can do

Put GitHub to work.

Link a PR to an issue by including the issue identifier (e.g. ENG-1234) in the branch name, PR title, or description — no manual linking step.
Automate status transitions: issues move to In Progress when a linked PR opens and to Done when it merges, following rules you configure per team.
See linked branches, PRs, and review state directly on the issue so reviewers have full context.
Copy a ready-made branch name (with the issue identifier baked in) from the issue, so naming stays consistent across the team.

Great for

Where GitHub pulls its weight.

Engineers never touch issue status manually — it follows the PR.
PMs see exactly which PRs are tied to a feature without asking.
Standardize branch naming across a team with one-click copy.

Setup

Connect GitHub in minutes.

Install the GitHub appFrom Settings → Integrations, choose GitHub and install the Planoda GitHub app on your organization. Grant access to the repositories you want linked.
Map repositories to teamsAssign each connected repository to one or more teams so issue identifiers resolve to the right workspace.
Choose automation rulesPick which workflow states a PR opening and merging should move issues to. Defaults are sensible; override per team as needed.
Open a linked PRCreate a branch or PR referencing an issue identifier like ENG-1234. The PR appears on the issue and status follows your rules.

FAQ

GitHub integration FAQ.

Works with

More developer tools integrations.

Don't see what you need? Build it on our API, SDK, and MCP server.

Where this fits

How teams use GitHub in their workflow.

Ready to connect?

Connect GitHub to Planoda.

Get started — free Take the tour