Skip to content
Source
Sign inSign up

Work on items from GitHub

Move from GitHub / Sync

Work on items from GitHub

An issue or a pull request from GitHub is on both sides, so what you do on it here goes to GitHub. See who can act on these items, and how your text, files and reactions show on GitHub.

5 min read

To act on these items, connect GitHub for sync first. See Connect GitHub.

Who can act on items from GitHub

  • People who connected GitHub: the action goes to GitHub first, under their GitHub account. If GitHub refuses it, nothing changes here, and you see the reason from GitHub.
  • People who did not connect: refused, with a link to connect.
  • Agents: it depends on who started the run. See What agents can do.

You need the permission on GitHub as well as here.

What agents can do

A run that starts by itself (on a new item, a push or a label) acts as the bot, here only:

  • Its comments and reviews stay here, with an Only here mark.
  • It does not label or assign the item on GitHub.

A run that you start by hand acts on GitHub as you, with your GitHub token:

  • Comments and reviews: they go to GitHub after screening shows them here. They end with a line that names the agent, for example "Written by an automatic PR review agent." A review goes up when each of its line notes is decided. A line note that a maintainer rejects stays out.
  • Labels: they go to GitHub at once. This includes the label that your audit adds for a maintainer. If they cannot go, they change here only.
  • Assignees: they go to GitHub first. If GitHub refuses, nobody is assigned.
  • Text that points here: when the text links to this site, the agent gets it back, and writes it again.
  • When it cannot act as you: you have no GitHub connection, you lost write access, or GitHub refuses. The comment or the review then stays here, with an Only here mark.

Any agent can also:

No agent can:

  • Close, reopen, mark a draft or ready for review, rename, edit, resolve threads on, or merge an item from GitHub.
  • Edit a comment that is on GitHub.
  • Open a pull request on GitHub.
  • Update the branch of a pull request from GitHub, or apply a CI fixup to it. A person does it.

Push to the head branch of a pull request

A pull request from GitHub has its head branch on GitHub. Two actions of a person push to that branch, with the person's own GitHub token:

GitHub takes the push first. The head here moves only after that. If GitHub refuses the push, nothing changes here, and you see the reason.

Your text on GitHub

GitHub shows your text as you wrote it. So the editor warns you when your text links to this site. To name an item, use its GitHub number. When it is not the number here, the page of the item shows it, for example "(GitHub #7)".

Attached images and videos

An attached file links to the assets of the repository with a full URL. GitHub readers see the file only when those assets are public:

  • Public repository, or a private one with Assets are public on: GitHub shows the file. The editor does not warn about the attached file.
  • Private assets: GitHub readers get no file. The editor warns: "GitHub readers will not see the attached files. The assets of this repository are private."

To make the assets public and keep the code private, see Who can see your assets.

Reactions

A person on GitHub reacts with πŸ‘ to an issue, and your team reacts here. You want both sides to show the same reactions.

Here to GitHub

  1. Connect GitHub. See Connect GitHub.
  2. React to an item from GitHub, or to one of its comments.

The reaction goes to GitHub first, under your GitHub account. If GitHub refuses it, nothing changes here. When you take the reaction back, it goes from GitHub too.

These reactions stay here:

  • A reaction of an agent. Agents react here only.
  • A reaction on a comment with the Only here mark. GitHub does not have that comment.

GitHub to here

  • GitHub tells this site nothing when someone reacts. So a reaction made on GitHub comes here the next time Source reads the item from GitHub. That happens when something else on the item changes on GitHub, for example a new comment, an edit or a label.
  • When Source reads the item, it also takes away the reactions that GitHub no longer has.
  • A reaction from GitHub shows as the account here of the person when their GitHub account is linked to it, else as their GitHub login. It notifies no one.
  • Source reads up to about 1,000 reactions from GitHub for one item and its comments. On an item with more, some reactions show a lower count here than on GitHub.