Skip to content

Explain gate-check 403s and refine installation health UX - #479

Open
morgaesis wants to merge 1 commit into
mainfrom
settings-health-ux
Open

Explain gate-check 403s and refine installation health UX#479
morgaesis wants to merge 1 commit into
mainfrom
settings-health-ux

Conversation

@morgaesis

Copy link
Copy Markdown
Contributor

Gate-enforcement lookup errors now include GitHub's X-Accepted-GitHub-Permissions header, so a permission-denied 403 (as seen on private repositories whose active branch rules the App cannot read) names the missing App permission instead of an opaque status code. The settings re-check buttons become refresh icon buttons showing when the last check ran and when the next automatic sweep is due, each setup plan gains a copy-agent-prompt button producing a self-contained work order for a coding agent, the shared owner configuration toggle warns inline when the source repository is missing from the App installation, and configured-but-unexercised config files render with neutral styling instead of error styling. Covered by the gate-enforcement, rate-limit, and settings test files plus a clean production build.

Surface GitHub's X-Accepted-GitHub-Permissions header in gate-enforcement
lookup errors so a permission-denied 403 names the missing App permission
instead of an opaque status code. Turn both settings re-check buttons into
refresh icon buttons that show when the last check ran and, for installation
health, when the next automatic sweep is due. Add a copy-agent-prompt button
to each setup plan that produces a self-contained work order for a coding
agent. Warn on the shared owner configuration toggle when the source
repository is not in the App installation, and render unexercised config
files with neutral styling instead of error styling.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant