Skip to content
Workflows

GitHub App setup

Install Gittensory on a repo, then choose whether it should stay advisory or enforce repo-configured PR quality rules.

Install

  1. Open the Gittensory GitHub App listing.
  2. Choose the repositories you want to grant access to.
  3. Approve the requested permissions (issues, pulls, checks, metadata).

Default posture

Gittensory is advisory-first. Public comments, labels, the Context check, and the Gate check are controlled per repo. Missing issue links, non-Gittensor contributors, busy queues, and weak overlap signals do not block merge by default.

PR panel

The PR panel is one sticky bot comment that updates in place. It shows a public-safe readiness score, concrete signal evidence, and short actions for linked issues, related work, review load, validation evidence, open PR queue, contributor context, and Gate result.

Checks

Gittensory Context is advisory and should not be required in branch protection. Gittensory Gate is opt-in and can be made required after a repo owner chooses blocking rules.

Gate modes

Each Gate rule supports off, advisory, or block. Linked issue, duplicate PR, and quality-score checks default to advisory. The quality rule only blocks when qualityGateMode is block and aqualityGateMinScore threshold is configured.

Dogfood mode

For repos like JSONbored/gittensory and awesome-claude, enable PR comments, labels, Context, and Gate together to test the full product surface. If another maintainer agent can merge quickly, configure that agent to wait for Gittensory Gate before merge or close.

Install diagnostics

After installing, verify your install health from the API. The readiness endpoint separates service health from data quality.

Gittensory's GitHub App never requests source push, never stores repository contents, and never publishes wallet, hotkey, payout, trust, reward, or private scoring language.