#GitHub integration

The GitHub integration connects code hosting to your task flow. It is not the same as Repositories: this page covers pull request links, issue sync, and linkbacks. It does not give an Agent permission to clone code on a Computer.

#What the GitHub integration can do

• Connect GitHub for the organization. An Organization Owner or Admin installs the GitHub App and chooses repositories.
• Link pull requests to tasks. A task ID in the branch name, pull request title, or pull request body is enough to try a link. Linked pull requests can also get a linkback comment.
• Sync GitHub issues into a Space. After you link an installed repository to a Space, newly created issues become tasks.
• Connect a personal GitHub account. Members can connect their own GitHub account separately. Comments synced to a GitHub issue then try to use that person's GitHub identity.

#Where to open it

Open Integrations. GitHub is in the Git repositories group. The cards are GitHub and GitHub Issue. Use the labels in the product if they differ.

When a GitHub organization is connected and a personal account is not, the card shows the organization connection. It does not mean a personal GitHub account is connected.

#Connect a GitHub organization

Organization Owners and Admins can connect a GitHub organization.

1. Open Integrations, then the GitHub page.
2. Under Connect GitHub organizations, choose Connect.
3. Install the GitHub App and select the repositories for this install.
4. Return to Sharkly and confirm the status is Connected.

Only the person who actually manages that GitHub App install can finish the bind.

Disconnecting an organization stops pull request linking and linkbacks from that organization. Existing tasks and GitHub content are not deleted.

#Personal GitHub account

A personal GitHub account is separate from the organization connection.

• The organization connection controls whether repositories, pull request links, and issue sync can work.
• My GitHub account controls whose identity is used on GitHub issues. Without it, comments use the app bot identity.

After you connect, GitHub issues and comments you create are attributed to you when possible, and assignees can mirror both ways. A GitHub account already connected to another member cannot be connected to you.

#Pull requests and tasks

In Link git PRs & commits to tasks, you can toggle Link pull requests and Link git commits.

Write a task ID in:

• the pull request title;
• the pull request description;
• the source branch name.

A task ID is enough to try a link. Fixes ID-123 and a bare ID-123 both work.

There is no extra meaning for words such as fixes, closes, or skip. Merging a pull request does not change the task status.

On a public repository, only trusted authors are linked: the repository owner, a member, or a collaborator.

#Linkbacks

Linkbacks comment a task link on linked pull requests and GitHub issues. The switches live in GitHub settings:

• Private repositories: on by default;
• Public repositories: off by default.

Whether the Space is public or private is not the linkback switch.

#Issue sync

Link a GitHub repository to a Space so newly created GitHub issues sync as tasks. Existing issues are not imported.

Closing or reopening a GitHub issue can move the paired task's status. Merging a pull request does not.

Linking a private Space to a public repository when the direction would write content out (for example two-way) requires an explicit confirmation. Task titles, descriptions, and member comments would be public on GitHub.

Removing a repository link stops new issues from syncing. Tasks already created stay. Disconnecting GitHub sync for a single task also does not delete the task or the issue.

#Where comments go

The task's own comment box is internal discussion. It does not post to GitHub.

Only the GitHub comments from … block (Post to GitHub) writes to the linked issue. The same rule applies to Slack threads: outbound replies use that surface's own composer.

On a one-way repository, replies are not sent to GitHub.

#Common questions

#Does connecting GitHub let an Agent clone the repo?

No. Organization GitHub integration does not replace Git credentials on the Computer. Cloning still uses the Computer's SSH key, HTTPS token, or host credentials. See Repositories.

#Why does the card say an organization is connected if I still need to connect GitHub?

Organization bind and personal account are two steps. The organization connection is shared. The personal account only affects how your comments appear on GitHub issues.

#Does merging a pull request complete the task?

No. A task ID only tries to create a link. There is no fixes / closes keyword behavior, and a merge does not change task status.

#Does disconnecting GitHub delete tasks or issues?

No. Disconnecting the organization, removing a repository link, or disconnecting GitHub sync for one task leaves existing tasks and GitHub content in place.