GitHub integration

GitHub integration with per-person attribution

Link tasks to GitHub issues, branches and pull requests with commit tracking, where writes use each member's own token so actions are attributed to the person.

Included on Basic and up

app.planner.day/task/export-retrieslive

Linked work

#482Export retries drop the last batchOpen
PRfeat/export-retryMerged

Commits

a8f4339 fix: retry the tail batch Rahul
2e281b8 test: cover the 500-row boundary Aisha

Writes use each member's own token, so GitHub shows the person.

In one answer

Does Planner.day integrate with GitHub?

Yes. Tasks link to GitHub issues, branches and pull requests, with commit and pull request tracking surfaced on the task. Reads use a business-level token configured once by an admin, while writes use each member's own token, so an action taken from Planner.day is attributed in GitHub to the person who took it rather than to a shared bot account. Workflow rules can also create a GitHub issue or branch automatically.

Every project management tool integrates with GitHub. The differences are in the details, and one of them changes how the history reads.

Reads and writes use different tokens

Most integrations authenticate as a single connected account. Everything the tool does in GitHub is then attributed to that account, so the history fills with actions taken by a bot on behalf of somebody the log does not name.

Planner.day splits it. Reads use a business-level token, added once by an admin, which is what keeps issue, branch and pull request state current across the workspace. Writes use each member’s own token. When you close an issue or open a branch from a task, GitHub records that you did it, because you did.

That matters for the obvious auditing reason, and for a less obvious one: review and blame history stays useful.

What appears on the task

A task shows its linked issues, branches and pull requests, with commit and pull request activity tracked against it. Commit diffs are viewable from the task, so the common question of what actually changed does not require a context switch into GitHub.

Automation

Workflow rules can create a GitHub issue or a branch as an action. A triaged bug report can become a task and an issue in one step, or moving a task into a particular status can open the branch for it. See workflow automation.

Setup

An admin adds the business read token once, in organisation settings. Individual members add their own write token from their account settings, which takes about a minute and does not require admin involvement.