fix(workflows): disable lockdown on issue-triage-agent#60
Merged
Conversation
- remove lockdown:true so default GITHUB_TOKEN can be used - recompile issue-triage-agent.lock.yml - add gh-aw actions-lock.json 🔧 - Generated by Copilot
- add .github/actionlint.yaml ignoring SC2015 in *.lock.yml only - README.md: split adjacent code fences and add blank line above heading 🔧 - Generated by Copilot
sendtoshailesh
approved these changes
May 6, 2026
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
2 participants
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
Fixes failing run 25431693913 where the Issue Triage Agent failed with:
Changes
lockdown: truefrom.github/workflows/issue-triage-agent.mdso the workflow uses the standardGITHUB_TOKENissued by Actions..github/workflows/issue-triage-agent.lock.yml.gh-awaction lock at.github/aw/actions-lock.json.Why option B (no lockdown)
This is an internal Azure-org repo whose triage runs only against issues in the same repo and only writes labels/comments via gh-aw safe-outputs. The added overhead of issuing and rotating a fine-grained PAT (
GH_AW_GITHUB_TOKEN) is not warranted here.Test
After merge, manually re-trigger via: