Question 1

Should I use GitHub App or OAuth?

Accepted Answer

We recommend the GitHub App install for organizations because it supports fine-grained permissions and does not require a user seat. OAuth is useful for per-user analyses where you want Ana to act under the calling user's identity. Both methods can be configured simultaneously.

Question 2

Does Ana read private repos?

Accepted Answer

Yes, as long as the GitHub App or OAuth token has the repository:read scope. Admins control exactly which repos the TextQL GitHub App is installed on, and Ana cannot reach any repo outside that install scope even if the user has access elsewhere.

Question 3

How are GitHub tokens secured?

Accepted Answer

GitHub App installation tokens are short-lived and refreshed by TextQL transparently. OAuth tokens are encrypted in our credential vault. All tokens are injected at the network layer by our egress proxy, so Ana's sandbox never sees the raw value.

Question 4

Can Ana trigger GitHub Actions?

Accepted Answer

Yes with write scopes. By default the connector is read-only. Admins can enable workflow dispatch permissions so Ana can trigger runs, re-run failed jobs, or cancel long-running workflows. Writes are audit-logged and can be restricted to specific repos.

Question 5

Are GitHub rate limits handled?

Accepted Answer

Yes. The connector automatically backs off and retries when rate limits are hit. Using a GitHub App increases the available rate limit significantly compared to personal access tokens, which is the recommended setup for busy organizations.