You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow bots (e.g. github-actions) to label issues for Amazon Q agent features.
Use Case
It would be helpful if:
Amazon Q agent features could be triggered via GitHub Actions workflows
Things I tried:
Run a workflow that creates an issue to trigger the agent feature
create-issue.yml
name: Create Issueon:
workflow_dispatch: # Or whateverjobs:
create-issue:
runs-on: ubuntu-latestpermissions:
issues: writesteps:
- name: Create an issueuses: actions/github-script@v7with:
github-token: ${{ secrets.GITHUB_TOKEN }}script: | const title = "Test Issue"; const body = "Generate docs and create a new PR"; // Or whatever const labels = ["Amazon Q development agent"]; // Adding this label is supposed to trigger the agent feature await github.rest.issues.create({ owner: context.repo.owner, repo: context.repo.repo, title, body, labels });
Result:
✅ The trigger issue was successfully created
❌ The agent feature did NOT start (I'm assuming this is because the label was added by a bot github-actions)
It successfully starts when the label is manually added
🔴 Your role in this project doesn't include permissions to label issues for a generative AI assistant.
What I expect:
The agent feature successfully starts when the label is added via GitHub Actions
Proposed Solution
No response
Other Information
Note
This request is based on the assumption that it fails because the label is added by a bot. Please let me know if this assumption is incorrect. Any ideas for a workaround would also be appreciated.
Describe the feature
Allow bots (e.g.
github-actions) to label issues for Amazon Q agent features.Use Case
It would be helpful if:
Things I tried:
create-issue.yml
Result:
github-actions)What I expect:
Proposed Solution
No response
Other Information
Note
This request is based on the assumption that it fails because the label is added by a bot. Please let me know if this assumption is incorrect. Any ideas for a workaround would also be appreciated.