Add setup handler to auto-create coverage workflow PRs#2292
Merged
hiroshinishio merged 3 commits intomainfrom Feb 20, 2026
Merged
Add setup handler to auto-create coverage workflow PRs#2292hiroshinishio merged 3 commits intomainfrom
hiroshinishio merged 3 commits intomainfrom
Conversation
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
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
setup_handlerthat runs on install: detects repo language from root files, creates a PR with the appropriate GitHub Actions coverage workflow YAMLclose_pull_requestAPI helper for cleanupVERIFY_TASK_IS_COMPLETEinto_TOOLS_BASEso all handlers (issues, PRs, setup) use itverify_task_is_completebug: no PR file changes now returns success (setup handler may determine no workflow is needed)/api/{owner}/{repo}/setup_coverage_workflowtest_clone_and_installandtest_process_repositoriestests broken by function signature and import changesSocial Media Post (GitAuto)
GitAuto's coverage dashboard shows your files after install, but if you don't have a CI workflow that runs tests and uploads coverage data, the percentages and charts stay empty. That setup step is where most users got stuck. Now on install, GitAuto detects your language and opens a PR with the right CI workflow. Merge it and coverage data starts flowing.
Social Media Post (Wes)
After installing GitAuto, the coverage dashboard shows your files but coverage percentages and charts are empty if you don't already have a CI workflow that runs tests and uploads an LCOV report. Setting that up is where most users drop off - honestly I would too. So we automated it. On install, we detect the language from your repo and open a PR with the right CI workflow. Merge it and coverage data starts flowing.