DocsConnect your infrastructure

Git accounts and the GitHub App

Give OpsNexa Online access to your private repositories, so it can deploy them, check them on every push and open pull requests with fixes.

OpsNexa Online needs access to your code to deploy private repositories, check them on every push, and open pull requests with fixes. There are two ways.

The GitHub App is OpsNexa Online’s own app on your GitHub organization. Nothing is tied to a person, so it keeps working when people leave.

  1. Open Connections, find Git accounts and press Create the GitHub App.
  2. GitHub shows the app and the permissions it asks for: code and pull requests (read and write), commit statuses and workflows. Confirm.
  3. Install it on your organization and pick the repositories it may see.
  4. Those repositories appear under Repositories and are checked straight away.

One webhook brings every push and pull request to OpsNexa Online instantly. Git and the API use one-hour tokens. GitHub Enterprise Server works too.

A git account with a token

For GitLab, Gitea, Bitbucket, self-hosted servers, or if you prefer a token on GitHub:

  1. Open Connections → Add connection and choose Git account.
  2. Pick the provider. For a self-hosted server, enter its server URL.
  3. Paste an access token:
    • to deploy and check code, reading is enough (GitHub: Contents: read; GitLab: read_repository);
    • to open pull requests with fixes, allow writing too (GitHub: Contents and Pull requests: read and write; GitLab: api).
  4. Press Add. The token is used for every private repository on that account.

What it’s used for

Without write access, OpsNexa Online still checks everything, and you can download any fix as a patch.

Something unclear or missing? Tell us, or press the ? at the top of OpsNexa Online for the guide and tours inside the product.