Skip to content

GitHub

Connect GitHub repositories to Project Feed projects. Sync issues, tasks, and comments, and choose which events appear in the feed.

Connect one or more GitHub App installations, then map repositories to projects. Repository activity lands in the feed, issues sync with tasks, and commits and pull requests attach themselves to the tasks they mention.

  • Publish pushes, pull requests and reviews, workflow runs, deployments, releases, and issues to a project feed
  • Track all branches, including future branches, or search and select branch names for each mapping
  • Show events as activity updates, or publish each one as its own post
  • Sync repository issues with project tasks, one way or both ways
  • Attach commits, pull requests, and branches to the tasks they name, and move those tasks across the board
  • Create a GitHub issue from a task, or import a repository's existing issues
  • Connect several GitHub accounts to one workspace
  • Share a project connection across projects without moving its mappings or synced tasks

How GitHub sync works

Connections and mappings

A connection links your workspace to a GitHub App installation. Add a mapping to choose which Project Feed project receives each repository's activity. Nothing syncs until you add a mapping. Mappings also control event types, branch filters, and feed style, and you can edit them after creation.

Issues and tasks

By default, issues become tasks, and issue changes and comments update those tasks. Turn on two-way sync on a mapping to mirror a task's title, description, and status back to its issue. Completing the task closes the issue. A later change in GitHub can overwrite an edit to the same field in Project Feed.

Create GitHub issue in the task menu sends a single task to the mapped repository. A mapping can also create an issue for every new task in its project. That is off by default, and only one mapping per project can do it across GitHub and Jira. Select Import existing issues on the mapping row to bring in older issues and their comments. Already synced issues are skipped.

References and automation

Any commit message, pull request title or description, or branch name that contains a task identifier such as PRO-123 attaches that commit or pull request to the task. This works for every repository in the installation, mapped or not. Pushing a branch named after a task moves it to In progress, opening the pull request moves it to In review, and merging completes it. Closing words like fixes PRO-123 complete the task when the pull request merges or the commit lands on the default branch. Each project’s settings can repoint or disable these rules. Every task also has a copyable branch name, such as username/pro-123-fix-login-redirect.

Comments and mentions

Comments cross in both directions with headings, lists, code blocks, quotes, and links intact. Checklist items reach GitHub as bullets marked [x] or [ ]. GitHub issue comments are flat because GitHub has no comment threading. Comments written in Project Feed carry a short attribution line naming the author.

An @mention of a mapped workspace member becomes a real mention on the other side, and Project Feed mentions go out as @login. Members map themselves by linking their GitHub account in account settings, and admins can fill in the rest from the People list on the connection page. Names that cannot be placed stay plain text.

Project Feed credits activity to a mapped workspace member when one exists, and otherwise shows the GitHub username. Changes made by Project Feed appear under the app's bot account. Referenced issues and pull requests also get one Project Feed comment listing their linked tasks, updated in place as references change.

Connect GitHub

  1. 1.

    Authorize the provider

    Install the Project Feed GitHub App for the repositories the workspace needs.

  2. 2.

    Configure the connection

    Choose a repository and destination project, then select events, branches, feed style, issue sync, and write-back. A repository can sync issues into only one project; other mappings can still publish activity.

  3. 3.

    Verify the mapping

    Check the mapping status, then create or update a test issue, pull request, or commit reference.

GitHub repository mapping

A workspace can connect up to 50 GitHub accounts, one GitHub App installation each, and every project can map repositories from any of them. A project admin can also connect a GitHub account from the project's integration settings. That connection is available only to the project it was added from. Workspace admins see it in workspace settings and can disconnect it there. Add a mapping for each repository and project feed, then choose events and optional branch filters. Branch filters also apply to workflow runs, deployment statuses, and pull request reviews. The same repository can publish to more than one project. Pushes to different branches remain separate updates, even when the branches point at the same commit.

GitHub access and disconnecting

  • Workspace owners and admins manage GitHub connections and can share a project connection with the workspace. A project admin can connect an account for that project only.
  • Project Feed can read only the repositories you grant when installing the GitHub App. It writes to GitHub only after a mapping turns on two-way sync or issue creation.
  • To disconnect an account, open its menu on the GitHub page and choose Disconnect. Its repository mappings stop publishing and existing feed posts stay.

Fix GitHub connection problems

A repository is not available to map
Review the GitHub App installation and grant it access to the repository. Return to Project Feed, refresh the connection, and create the mapping after the repository appears.
Expected activity is missing
Check the mapped event types and branch filter, then confirm the repository is still covered by the installation. Generate one test event that matches the filter.
Write-back remains read-only
Enable two-way sync on the mapping and have a GitHub organization owner approve updated app permissions when prompted. An installation that predates write-back may need that approval before Project Feed can write anything. Recheck the mapping status before editing a synced task.
A commit or pull request did not attach to a task
Put the exact task identifier in the commit message, pull request title or description, or branch name. Confirm the task belongs to this workspace and the repository is in the connected installation.
A mention stays plain text
Mentions cross only when Project Feed knows the person on the other side. Ask the member to link their GitHub account in account settings, or have an admin match them in the People list on the connection page.
A pushed task status moved back or did not move
Automation only moves tasks forward, so a status you set by hand is never pulled backward. Check the project's git automation settings, which can repoint or disable each rule.
Image preview
100%