Split handler configs into regular and project handlers #13221
Closed
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.
The JavaScript handler manager expected project handlers in
GH_AW_SAFE_OUTPUTS_PROJECT_HANDLER_CONFIG, but the compiler generated a singleGH_AW_SAFE_OUTPUTS_HANDLER_CONFIGcontaining all handlers. Project handlers (update_project,create_project,create_project_status_update) were never loaded.Changes
Compiler (
pkg/workflow/compiler_safe_outputs_config.go)handlerRegistryintoregularHandlerRegistryandprojectHandlerRegistryGH_AW_SAFE_OUTPUTS_HANDLER_CONFIG- regular handlers (add_comment, create_issue, etc.)GH_AW_SAFE_OUTPUTS_PROJECT_HANDLER_CONFIG- project handlers requiring separate Octokit clientTests
Workflows
Result
Compiled workflows now generate both configs:
The unified handler manager loads project handlers from the separate config and initializes them with the project Octokit client.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.