Oynix
GitLab

Connectors / GitLab

Your GitLab repos and the reasoning behind them.

Parse your GitLab repositories and merge requests into one knowledge graph, self-managed instances included.

One tapYour own OAuth appA token you paste

Before you start

Install Oynix and open the connectors page. You do this once. Everything below then happens right in the page, with no commands to run.

Install OynixOpen the connectors page

Log in

Pick whichever you prefer. You only need one.

One tap

Click, approve, done.

  1. 1In the connectors page, open GitLab and click "Connect with GitLab".
  2. 2A provider window opens. Sign in and approve the read-only scopes.
  3. 3It closes and you are connected. There is nothing to copy or paste.

Your own OAuth app

Register an app once.

  1. 1In GitLab → Preferences → Applications, add a new application.
  2. 2Set the redirect URI from the connect panel and the read_api / read_repository scopes.
  3. 3Copy the Application ID and Secret.
  4. 4In Oynix pick 'Use your own app', paste both, then Connect.

A token you paste

Paste a credential.

  1. 1Create the credential: GitLab → Preferences → Access Tokens, with the read_repository scope.
  2. 2Open GitLab in the connectors page and choose the token path.
  3. 3Enter the repo as owner/name, the token, and your host URL if self-hosted, then click Connect. Oynix checks it right then and saves nothing if it fails.

After login

Once connected, this all happens in the page. No commands.

  1. 1The repository manager opens. Add one or more repos as owner/name.
  2. 2Each repo indexes as its own project, with progress shown.
  3. 3Hit Sync anytime to refresh it.

One-tap OAuth is gitlab.com only. Self-hosted instances connect with a token.

What it syncs

Code

Functions, classes, files and their call and import edges, parsed at the AST level.

Merge requests

MR descriptions and discussion, linked to the changed code.

History

Authorship and change history: who changed what, and when.