Repository navigation
Conversation
The wizard's GitHub gate is becoming skippable, so the skill can no longer assume the App is connected. Step 5 leaves GitHub Issues out of the ask when the run prompt says GitHub was skipped, 5a refuses to create a source without a github integration, and the report records GitHub as skipped with a connect follow-up. Drop the "github connection declined" abort from the advertised list so a missing connection never reads as a reason to end the run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
Collaborator
Author
|
Closing alongside PostHog/wizard#1407: GitHub stays required for now. The gate fix is PostHog/wizard#1409, which needs no skill change. |
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.
Stops the self-driving setup skill from assuming the PostHog GitHub App is connected, since the wizard now lets users skip it. Users who skip get a run without GitHub Issues and a report that says GitHub was skipped, with a connect follow-up. Maintainers no longer see
[ABORT] github connection declinedadvertised, so an agent never ends a run over a missing App.What's new
5a-github.mdguard. Nogithubintegration means create nothing, go dormant.[ABORT] github connection declined. Two abort strings remain.How it flows
%%{init: {"block": {"padding": 20}}}%% block-beta columns 3 wizardBand["wizard run prompt outside this repo"]:3 prompt["The PostHog GitHub App is NOT connected"]:3 skillBand["context/skills/self-driving changed"]:3 ask["5-connected-tools.md ask"]:3 connector["5a-github.md"]:3 report["7-report.md"]:3 prompt --> ask ask -- "GitHub Issues left out" --> connector connector -- "dormant fallback" --> report classDef new fill:#3b82f626,stroke:#3b82f6,stroke-width:2px classDef ext fill:none,stroke:#9ca3af,stroke-dasharray:4 3 classDef newBand fill:#3b82f640,stroke:none classDef oldBand fill:#9ca3af40,stroke:none class ask,connector,report new class prompt ext class skillBand newBand class wizardBand oldBandOne lane, top to bottom: the wizard's prompt says GitHub was skipped, and each step reads that. Blue changed here, and the dashed prompt comes from the wizard PR. 5a only runs if an agent reaches it anyway, so its guard is the backstop.
5-connected-tools.md,5a-github.md,7-report.mddescription.mdThe connected-tools ask
Step 5 keeps GitHub Issues in the SaaS basics, except when the run prompt says GitHub was skipped. It can't connect without the App, so offering it would only produce a dormant source.
The GitHub connector
5a-github.mdgains a "No GitHub App" paragraph. With nogithubintegration on the project, it creates nothing and takes the existing dormant fallback with a connect follow-up.The report
The GitHub row reads connected, or skipped with a follow-up to connect the App at the integrations settings URL. The abort list in
description.mddrops[ABORT] github connection declinedand says a missing App isn't a reason to stop.Details and verification
pnpm test: 27 files, 215 tests pass.pnpm build: 11 plugins, 139 skills.github connection declinedfor older cached skills, so dropping it here breaks nothing.CONTEXT_MILL_PATHin$WORKBENCH/.envat this branch, run the skip path, and check steps 7 and 8 there: no GitHub Issues row in the step 5 ask, and the report's GitHub row says skipped with the follow-up.🤖 Generated with Claude Code