Document previous-result strategies for scheduled workflows - #54568
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
Document scheduled workflow result strategies
Document previous-result strategies for scheduled workflows
Aug 21, 2026
Copilot created this pull request from a session on behalf of
pelikhan
August 21, 2026 16:47
View session
pelikhan
approved these changes
Aug 21, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds lifecycle guidance for handling previous outputs from scheduled workflows.
Changes:
- Documents wait, replace, and preserve-history strategies.
- Removes an obsolete generated router suppression comment.
Show a summary per file
| File | Description |
|---|---|
.github/aw/create-agentic-workflow.md |
Adds previous-result authoring guidance. |
.github/workflows/agentic_commands.yml |
Removes a runner-guard suppression comment. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
| For every daily or scheduled workflow that creates issues or pull requests, choose the strategy that best matches the workflow's goal: | ||
|
|
||
| - **Wait for the previous result** when only one active result should exist. Configure `on.skip-if-match` to skip the entire agent execution while the issue or pull request created by an earlier run remains open. The workflow resumes after that item is closed or merged. | ||
| - **Replace previous results** when the newest result supersedes older reports. For issues, configure `safe-outputs.create-issue.close-older-issues: true` and use `close-older-key` when an explicit matching key is needed. |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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
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.
Scheduled agentic workflows need an explicit strategy for handling issues or pull requests created by earlier runs. The authoring guidance now requires choosing the strategy that best matches the workflow’s lifecycle.
on.skip-if-matchwhile a previous issue or pull request remains open.close-older-issuesand, when needed,close-older-key.