GitHub sync

GitHub sync connects Tree nodes to GitHub issues or pull requests. The sync is bidirectional: changes in either system propagate to the other, keeping the node and the GitHub object aligned.

What gets synced

The sync keeps these properties aligned:

• Status: closing a GitHub issue marks the corresponding Tree node complete, and vice versa
• Title: changes to the issue or node title sync in both directions
• Description: the body of the issue and the description of the node stay in sync
• Assignment: on Team workspaces, GitHub assignees map to Tree assignments
• Labels and tags: GitHub labels map to Tree tags

Comments and activity are not currently synced. They live separately on each platform.

How nodes are linked

A node can be linked to:

• An existing GitHub issue or PR: paste the URL into the node, and the link is established
• A new GitHub issue created from the node: a "create GitHub issue" action creates the issue in the configured repository and links it automatically

Each node can be linked to one GitHub object. Multi-link is on the roadmap but not currently supported.

Repository configuration

GitHub sync requires:

• A GitHub account or organization connected via OAuth
• A target repository configured per project (or per workspace, for default routing)
• Appropriate permissions on the repository for the sync to read and write

The setup is one-time per workspace.

Tier availability

GitHub sync is part of the core feature set, available on Free, Paid, and Team.

Related

• Import from other tools
• Webhooks
• API access