Skip to content

Add skip-if-already-ran action for scheduled runs on an unchanged commit - #206

Merged
woksin merged 2 commits into
mainfrom
workflows-205-skip-same-commit-schedules
Oct 24, 2026
Merged

woksin merged 2 commits into
mainfrom
workflows-205-skip-same-commit-schedules

Conversation

@woksin

@woksin woksin commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Added

Scheduled workflows that validate their own commit can skip when the same
workflow already succeeded on the same head SHA. Manual dispatches and
re-runs always run, and any API error runs normally.
The offline test created its temporary directory under the gitignored
.ai-work folder, which a fresh CI checkout does not have. Event lists
with spaces after the commas now match too.
@woksin woksin self-assigned this Oct 24, 2026
@woksin

woksin commented Oct 24, 2026

Copy link
Copy Markdown
Contributor Author

Reviewer notes

  • Wave 1 of Skip scheduled runs when the workflow already ran on the same commit #205: the action, its offline test (.github/scripts/tests/skip-if-already-ran.test.py, 14 tests), a verify-skip-if-already-ran workflow and the README section. No caller adopts it yet; adoption in Screenplay, Stage and Chronicle follows separately.
  • Local: the skip test passed (also from a fresh git archive tree), workflow-lint, cache-actions test and actionlint passed.
  • Cross-provider review (Opus + Sol): round 1 found the test depended on .ai-work/; fixed in 4a0a9a6. Round 2 passed with no findings.
  • Not part of the bootstrap push paths: merging triggers no organization-wide write workflow.

@woksin
woksin merged commit 316695c into main Oct 24, 2026
12 checks passed
@woksin
woksin deleted the workflows-205-skip-same-commit-schedules branch October 24, 2026 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant