Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 14, 2025

All workflow stop-after fields now use +1 month instead of the previous mix of +48h and +30d values.

Changes

  • 15 workflow files: Updated stop-after from +48h or +30d to +1 month
    • Comments updated to reflect "1 month" where previously stated "48 hours" or "30 days"
  • Documentation: Updated docs/daily-progress.md timeout protection reference

Example

- stop-after: +48h # workflow will no longer trigger after 48 hours
+ stop-after: +1 month # workflow will no longer trigger after 1 month
- stop-after: +30d # workflow will no longer trigger after 30 days. Remove this and recompile to run indefinitely
+ stop-after: +1 month # workflow will no longer trigger after 1 month. Remove this and recompile to run indefinitely
Original prompt

Update all "stop-after" fields to use "+1 month"


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Update stop-after fields to use +1 month Standardize stop-after fields to +1 month across all workflows Nov 14, 2025
Copilot AI requested a review from pelikhan November 14, 2025 13:45
@pelikhan pelikhan marked this pull request as ready for review November 14, 2025 17:02
@pelikhan pelikhan merged commit ea35016 into main Nov 14, 2025
2 checks passed
@pelikhan pelikhan deleted the copilot/update-stop-after-fields branch November 14, 2025 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants