Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Feb 2, 2026

The JavaScript handler manager expected project handlers in GH_AW_SAFE_OUTPUTS_PROJECT_HANDLER_CONFIG, but the compiler generated a single GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG containing all handlers. Project handlers (update_project, create_project, create_project_status_update) were never loaded.

Changes

Compiler (pkg/workflow/compiler_safe_outputs_config.go)

  • Split handlerRegistry into regularHandlerRegistry and projectHandlerRegistry
  • Generate two environment variables:
    • GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG - regular handlers (add_comment, create_issue, etc.)
    • GH_AW_SAFE_OUTPUTS_PROJECT_HANDLER_CONFIG - project handlers requiring separate Octokit client

Tests

  • Updated assertions to expect project handlers in separate config

Workflows

  • Recompiled affected workflows (smoke-project, security-alert-burndown, test-project-url-default)

Result

Compiled workflows now generate both configs:

env:
  GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: '{"create_issue":{...},"add_comment":{...}}'
  GH_AW_SAFE_OUTPUTS_PROJECT_HANDLER_CONFIG: '{"update_project":{...},"create_project_status_update":{...}}'

The unified handler manager loads project handlers from the separate config and initializes them with the project Octokit client.

Original prompt

Fix Error: No handler loaded for type 'update_project'. See:
https://github.com/githubnext/gh-aw/actions/runs/21580319979


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 2 commits February 2, 2026 07:08
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix error handling for update_project type Split handler configs into regular and project handlers Feb 2, 2026
Copilot AI requested a review from mnkiefer February 2, 2026 07:14
@pelikhan pelikhan marked this pull request as ready for review February 2, 2026 07:17
@pelikhan
Copy link
Contributor

pelikhan commented Feb 2, 2026

Trying other fix. Wait for merge.

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.

3 participants