Skip to content

feat(issue-triage): expose GH_AW_GITHUB_TOKEN in workflow_call contract - #1026

Closed
fr4nc1sc0-r4m0n with Copilot wants to merge 3 commits into
mainfrom
copilot/modify-gh-aw-issue-triage-agent
Closed

feat(issue-triage): expose GH_AW_GITHUB_TOKEN in workflow_call contract#1026
fr4nc1sc0-r4m0n with Copilot wants to merge 3 commits into
mainfrom
copilot/modify-gh-aw-issue-triage-agent

Conversation

Copilot AI commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

The issue-triage reusable workflow had no way for callers to pass an ephemeral token, so comments applied by the workflow always used the built-in GITHUB_TOKEN, which cannot re-trigger downstream event-driven workflows.

Changes

  • .github/workflows/gh-aw-issue-triage.md — adds optional GH_AW_GITHUB_TOKEN to workflow_call.secrets; the runtime already consumed it via fallback chains, it just wasn't part of the public contract
  • .github/workflows/gh-aw-issue-triage.lock.yml — propagates the same secret into the compiled lock file
  • gh-agent-workflows/issue-triage/README.md — adds a Secrets table, matching the pattern established by dependency-review
  • gh-agent-workflows/issue-triage/example.yml — adds commented-out GH_AW_GITHUB_TOKEN wiring with explanatory comment
  • docs/workflows/gh-agent-workflows/issue-triage.md — adds Secrets table and updates example snippet

Usage

jobs:
  run:
    uses: elastic/ai-github-actions/.github/workflows/gh-aw-issue-triage.lock.yml@v0
    secrets:
      COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
      # Optional: ephemeral token so issue events from this workflow re-trigger downstream workflows
      GH_AW_GITHUB_TOKEN: ${{ secrets.GH_AW_GITHUB_TOKEN }}

…issue-triage workflow contract

Agent-Logs-Url: https://github.com/elastic/ai-github-actions/sessions/de2d5f43-9a2f-4a7c-a952-c93e94c41408

Co-authored-by: fr4nc1sc0-r4m0n <215478872+fr4nc1sc0-r4m0n@users.noreply.github.com>
Copilot AI changed the title [WIP] Update issue triage workflow to use ephemeral token feat(issue-triage): expose GH_AW_GITHUB_TOKEN and GH_AW_GITHUB_MCP_SERVER_TOKEN in workflow_call contract Apr 27, 2026
Copilot AI requested a review from fr4nc1sc0-r4m0n April 27, 2026 10:28
@fr4nc1sc0-r4m0n

Copy link
Copy Markdown
Contributor

@copilot remove the usage of GH_AW_GITHUB_MCP_SERVER_TOKEN

…act and docs

Agent-Logs-Url: https://github.com/elastic/ai-github-actions/sessions/dbd21aa5-27cf-4b31-a22d-107aad812093

Co-authored-by: fr4nc1sc0-r4m0n <215478872+fr4nc1sc0-r4m0n@users.noreply.github.com>

Copilot AI commented Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

@copilot remove the usage of GH_AW_GITHUB_MCP_SERVER_TOKEN

Done — removed GH_AW_GITHUB_MCP_SERVER_TOKEN from the workflow contract (gh-aw-issue-triage.md, gh-aw-issue-triage.lock.yml) and from both README/docs files in 15917cf.

Copilot AI changed the title feat(issue-triage): expose GH_AW_GITHUB_TOKEN and GH_AW_GITHUB_MCP_SERVER_TOKEN in workflow_call contract feat(issue-triage): expose GH_AW_GITHUB_TOKEN in workflow_call contract Apr 27, 2026
@fr4nc1sc0-r4m0n

Copy link
Copy Markdown
Contributor

@copilot I want you to change the target branch of this pr replacing main by copilot/add-classification-labels-input

Copilot AI commented Apr 28, 2026

Copy link
Copy Markdown
Contributor Author

@copilot I want you to change the target branch of this pr replacing main by copilot/add-classification-labels-input

I'm not able to change the base branch of a PR with the tools available to me. You can do it directly in the GitHub UI: open the PR, click Edit next to the title, and change the base branch to copilot/add-classification-labels-input from the dropdown.

@fr4nc1sc0-r4m0n

Copy link
Copy Markdown
Contributor

Done #1030

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.

Issue Triage can use Ephemeral Token

2 participants