Connecting GitHub

Linking your GitHub account, importing a repository into a project, and what unlinking does and does not touch.

View as .md

If you want your GitHub repo on Revquix, connect your account and import it. Connecting GitHub lets you bring a repository into a project and push your changes back.

Connecting#

Authorise Revquix from the GitHub panel. You are sent to GitHub, you approve, and you come back connected. The connection belongs to your account, not to one project - connect once and every project can use it.

Importing a repository#

Pick a repository and a branch, and its files become a project.

Two things to expect on a real repository:

  • Files the project cannot hold are skipped, and you are told which. The project has a 60-file and 256 KiB budget, and most repositories are larger. See project limits.
  • A file too large to run still imports. It is stored; it blocks a run until removed. That is deliberate - failing an entire import over one generated file nobody meant to execute would be worse.

Choosing what to import#

Import a folder rather than a monorepo where you can. A project is a place to work on something specific, and the limits are sized for that rather than for a whole codebase.

Unlinking#

Unlinking a repository from a project stops the push relationship.

Disconnecting your GitHub account entirely does the same across every project.

Was this page helpful?

Last checked against the product on . Behaviour changes are listed in the changelog.