Skip to content

feature: honour inputs for reusable workflows #56584

Closed

Description

@v1v

Similarly explained at #29189

but the idea is

on:
  workflow_call:
    inputs:
      report-failure-as-issue:
        default: true
        description: When true, agent failures are reported as GitHub issues
        required: false
        type: boolean

...



          GH_AW_FAILURE_REPORT_AS_ISSUE: ${{ inputs.report-failure-as-issue && 'true' || 'false' }}

this can help with configuring https://github.github.com/gh-aw/reference/safe-outputs/#failure-issue-reporting-report-failure-as-issue with some dynamism instead of using static code like

on:
  workflow_call:

safe-outputs:
  report-failure-as-issue: false

Why? Because otherwise, I need to use a post-compile hook:

Activity

  1. locked and limited conversation to collaborators on Aug 28, 2026
  2. unlocked this conversation on Aug 28, 2026
  3. locked and limited conversation to collaborators on Aug 28, 2026
  4. unlocked this conversation on Aug 28, 2026
  5. fr4nc1sc0-r4m0n commented on Sep 10, 2026

    @fr4nc1sc0-r4m0n

    I think that could make sense to include report-failed-jobs safe output as an input as well. Requested here #56584 (comment) too

  6. locked and limited conversation to collaborators on Sep 10, 2026
  7. unlocked this conversation on Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions