You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
generate short-lived GitHub App tokens for sync and promotion workflows instead of pushing with GITHUB_TOKEN
validate App token wiring, permissions, Actions enablement, and repository credential metadata in patchlane doctor
add patchlane verify-auth to dispatch and watch a correlated no-push sync
document the required App permissions and setup flow in the manual, migration guide, examples, and setup skill
Why
GitHub suppresses most workflow events caused by the built-in GITHUB_TOKEN. Although it can push Patchlane's generated branches, those pushes do not reliably start integration CI or the subsequent promotion workflow. The workflows also did not pass GH_TOKEN to the GitHub CLI.
The generated workflows now use an installation token with explicit Contents, Workflows, and optional Issues permissions. App-authored pushes trigger the expected workflow chain.
This PR enhances the patchlane doctor diagnostics to enforce GitHub App-based authentication in automation workflows. It adds validation that sync/promotion workflows use an App installation token (via actions/create-github-app-token@) with correct permissions, and verifies that the required App credentials (client ID variable and private key secret) are configured in the repository's Actions metadata. Comprehensive unit tests cover all new validation paths including error conditions and API failure fallbacks.
Confidence: 4/5 ◉◉◉◉○ Safe with minor fixes
Changes are well-scoped to doctor diagnostics only, with thorough test coverage; no breaking changes to existing behavior.
Blast Radius — 2 dependent repositories, 3 total references
The reason will be displayed to describe this comment to others. Learn more.
Mira Review Summary
The src/doctor.ts file introduces new doctor checks and automation validation logic without corresponding test coverage, flagged at line 432. Adding tests for this module would improve maintainability and help catch regressions as the GitHub App authentication workflows evolve.
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
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.
Summary
GITHUB_TOKENpatchlane doctorpatchlane verify-authto dispatch and watch a correlated no-push syncWhy
GitHub suppresses most workflow events caused by the built-in
GITHUB_TOKEN. Although it can push Patchlane's generated branches, those pushes do not reliably start integration CI or the subsequent promotion workflow. The workflows also did not passGH_TOKENto the GitHub CLI.The generated workflows now use an installation token with explicit Contents, Workflows, and optional Issues permissions. App-authored pushes trigger the expected workflow chain.
Validation
npm test(47 tests)npm run format:checknpm run artifacts:check