Link a repository
A repository you already have on GitHub, linked to your paper: with the App installed, its pushes are followed as they happen; without it, it is read every night. It stays where it is, in your account; OSCR copies nothing of it but what its licence allows.
The App is installed on GitHub. Name one of the repositories you gave it, below, to link it.
Who may link it
A person who administers or maintains the repository on GitHub (repository roles): GitHub says so when you authorize. A private repository is never linked, and its name is kept nowhere. A paper you are a verified author of is linked at once; another is proposed to its authors.
With the App, or without it
- With the App
- GitHub tells OSCR of each push, rename, archive or deletion as it happens (a webhook, signed by GitHub and checked), so the repository's page and its tracing maps follow at once. The App may read the repositories you choose when you install it, and later post its checks on pull requests. It never pushes code, never reads a private repository you did not give it, and you remove it at any time fromyour GitHub settings (about GitHub Apps).
- Without it
- The repository is read only, the way anyone reads a public repository: OSCR checks its head every night, so its page may be a day behind.
What linking does not do
It moves nothing and copies no history: git goes on to GitHub as before, with your own credentials. Refs such as pull requests' (refs/pull/…) are never mirrored. To bring code from another host, import it first; to start a new repository, create one.