[Draft] Add agentic workflow to comment on release notes PRs#2206
[Draft] Add agentic workflow to comment on release notes PRs#2206mazhelez wants to merge 1 commit intomicrosoft:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR replaces a legacy PowerShell script with a GitHub Agentic Workflow that can be manually dispatched to find open PRs modifying RELEASENOTES.md and post a standardized reminder comment after a release.
Changes:
- Deleted the previous
Internal/Scripts/CommentOnExistingReleaseNotesPrs.ps1implementation. - Added an agent prompt definition (
.md) describing how to detect the current release and which PRs to comment on. - Added the compiled gh-aw workflow lock file (
.lock.yml) that runs the agent and applies Safe Outputs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
Internal/Scripts/CommentOnExistingReleaseNotesPrs.ps1 |
Removes the prior standalone gh-based PowerShell implementation. |
.github/workflows/CommentOnReleaseNotesPRs.md |
Defines the agent instructions and Safe Outputs configuration for commenting on release-notes PRs. |
.github/workflows/CommentOnReleaseNotesPRs.lock.yml |
Adds the compiled workflow that executes the agent and performs comment writes via Safe Outputs. |
|
|
||
| safe-outputs: | ||
| add-comment: | ||
| allowed-repos: [microsoft/AL-Go] |
There was a problem hiding this comment.
The workflow is intended to add a comment to each open PR that touches RELEASENOTES.md, but the Safe Outputs config doesn’t specify a max for add-comment. In the compiled lock file this defaults to allowing only 1 comment per run, which will prevent processing multiple PRs. Set an appropriate max for add-comment (and re-run gh aw compile so the lock file updates) to match the expected number of PR comments.
| allowed-repos: [microsoft/AL-Go] | |
| allowed-repos: [microsoft/AL-Go] | |
| max: 50 |
|
|
||
| jobs: | ||
| activation: | ||
| runs-on: ubuntu-slim |
There was a problem hiding this comment.
runs-on: ubuntu-slim is not a standard GitHub-hosted runner label (e.g., ubuntu-latest, ubuntu-24.04). Unless you have a self-hosted runner with this exact label, this job will never start. Update the runner label to a valid GitHub runner (and recompile if this file is generated).
| runs-on: ubuntu-slim | |
| runs-on: ubuntu-latest |
| - detection | ||
| - safe_outputs | ||
| if: always() && (needs.agent.result != 'skipped' || needs.activation.outputs.lockdown_check_failed == 'true') | ||
| runs-on: ubuntu-slim |
There was a problem hiding this comment.
runs-on: ubuntu-slim is not a standard GitHub-hosted runner label. Unless there is a self-hosted runner matching it, the conclusion job will be stuck pending. Use a valid runner label (and recompile if this file is generated).
| runs-on: ubuntu-slim | |
| runs-on: ubuntu-latest |
| - agent | ||
| - detection | ||
| if: (!cancelled()) && needs.agent.result != 'skipped' && needs.detection.result == 'success' | ||
| runs-on: ubuntu-slim |
There was a problem hiding this comment.
runs-on: ubuntu-slim is not a standard GitHub-hosted runner label. Unless there is a self-hosted runner matching it, the safe_outputs job won’t run and no comments will be posted. Use a valid runner label (and recompile if this file is generated).
| runs-on: ubuntu-slim | |
| runs-on: ubuntu-latest |
mazhelez
changed the title
❔What, Why & How
Related to issue: #
✅ Checklist