feat(ui): maintainer onboarding — hero install button + config-as-code docs - #648
Merged
Conversation
…e docs - Homepage hero: add a prominent "Install the GitHub App →" CTA (one-click maintainer onboarding to github.com/apps/gittensory/installations/new), beside the Install MCP path. - GitHub App docs page: document `.gittensory.yml` config-as-code — the settings / gate / review blocks, precedence (.gittensory.yml > dashboard settings > defaults), and the public-safe footer guarantee (custom footer text, Gittensor register link always kept). - Add a worked, commented `review:` example to the repo's own `.gittensory.yml` (+ the bundled mirror, kept byte-identical) showing footer text, intro note, and per-row field toggles. UI typecheck + lint clean; backend typecheck + manifest/alignment tests pass. Note: visible UI change — hero/docs screenshots should be attached to the PR before merge.
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
ghost
added
the
|
gittensory · advisory review Reviewed 4 changed file(s) — two independent AI reviewers. Suggested action: ✅ Safe to merge — both reviewers found no blocking issues. Reviewer A · Suggestions
Worth double-checking
Reviewer B · Suggestions
Worth double-checking
Before = production · After = this PR's preview deploy.
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 07b77f2 | Commit Preview URL Branch Preview URL |
Jun 14 2026, 02:16 PM |
This was referenced Jun 14, 2026
JSONbored
added a commit
that referenced
this pull request
Jun 14, 2026
#681) Final round of the BYOK security-audit follow-ups (after #670, #680). - #673 Stand up a UI test runner (vitest + @testing-library/react + jsdom) in the gittensory-ui workspace and add the first component tests: the MaintainerPanel role gate (non-maintainer → "Maintainer access required", BYOK field never mounts; maintainer → dashboard) and AiReviewSettings (key field is write-only/password and never hydrates a stored key; provider/key mismatch is rejected client-side without a request; a valid key posts then clears). Wired `ui:test` into the CI "UI check" step. - #678 AI review panel UX + a11y: an initial loading state, an empty-state hint when no registered repos are detected, role="status" aria-live on the result banner, and aria-busy on the action buttons. - #675 Maintainer-facing BYOK documentation (docs/maintainer-byok-ai-review.md): how the advisory vs consensus layers work, that BYOK calls the provider directly and bills the maintainer (consensus always free), encrypted/write-only key handling, and dashboard vs .gittensory.yml config. Kept out of docs.github-app.tsx to avoid conflicting with the open onboarding-docs PR #648. Verified: ui:typecheck, ui:lint, ui:test (6 tests), ui:build, ui:openapi:check, actionlint, npm audit (0 vulns). Closes #673, #675, #678. Part of #525.
This was referenced Jun 14, 2026
JSONbored
added a commit
that referenced
this pull request
Jun 14, 2026
…amp (#701) (#708) Make the maintainer payoff self-evident at install: a repo-specific demo of what Gittensory would surface, plus a one-click advisory ramp. - `src/services/maintainer-activation.ts`: `buildMaintainerActivationPreview` runs the deterministic advisory engine (buildPullRequestAdvisory) over the repo's most recent PRs and returns "here's what Gittensory would have surfaced on N of your last M PRs" — per-PR findings + distinct finding-code counts + the current gate mode + whether AI review is configured + the single recommended next action. Pure over already-loaded data; NEVER runs AI (no surprise cost) — it only reports whether AI review is already on. - `recommendedAdvisoryActivationSettings()`: the one-click patch — enables the gate + deterministic rules in ADVISORY (non-blocking) mode, advisory-first per the #525 cross-cutting AC. AI review stays opt-in (separate ai-review route). - Routes (maintainer-scoped via requireRepoMaintainer; new `isRepoActivationPath` in canSessionAccessPath): GET `/v1/repos/:owner/:repo/activation-preview` and POST `/v1/repos/:owner/:repo/activation` (merges the advisory patch onto current settings, preserving unrelated fields). Reuses the existing gate engine + repo-settings infra (#647/#648); does not duplicate settings-preview (which previews ONE hypothetical PR — this previews the repo's REAL recent PRs). The dashboard rendering of this preview stays owner-led (visual). Email/AI live-preview remain out of scope. Tests: service unit (finding summary, recommended-action logic, AI-config flag, empty repo, sample-size clamp + recency fallback, code-count tie-break) + integration (maintainer preview + one-click flip persists; non-maintainer 403; server-to-server allowed). 97% coverage gate green; workers tests pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Makes installing + configuring Gittensory dead-simple for repo maintainers.
https://github.com/apps/gittensory/installations/new. Maintainers no longer have to dig through docs to find the install flow./docs/github-app) now documents.gittensory.yml— thesettings:/gate:/review:blocks, precedence (.gittensory.yml> dashboard settings > safe defaults), and the guarantee that custom footer text keeps the Gittensor register link/attribution.review:example in the repo's own.gittensory.yml(+ the bundled mirror, kept byte-identical) — footer text, intro note, and per-row field toggles, all commented.This builds on the config-as-code layer from #647.
Validation (from repo root)
npm --workspace @jsonbored/gittensory-ui run typecheck— cleannpm --workspace @jsonbored/gittensory-ui run lint— cleannpm run typecheck(backend) — cleangit diff --check— cleanUI evidence
CodeBlock/DocsPageprimitives.Notes
review:example is commented; the hero/docs are presentation only./docs/configroute could expand on this if you want config-as-code as its own page rather than a section.