Repository navigation
claw README: the */10 cron is best effort, measured gaps are hours (Closes #11132) - #11134
Merged
Merged
Conversation
…loses #11132) docs/claw/README.md said claw-t27f runs "every 10 minutes" and claw-merge "on the 10-minute schedule". Measured on master with the Actions API (event=schedule): the last 8 scheduled runs, 2026-10-18 12:11Z to 2026-10-19 13:50Z, were 2.1 to 7.5 hours apart. The README now says the cron is best effort and names pushes to master and workflow_dispatch as the dependable triggers. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 19, 2026 19:10
Contributor
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.
Closes #11132
docs/claw/README.mdclaimed thatclaw-t27fruns "every 10 minutes" andclaw-merge"on the 10-minute schedule". The cron is*/10, but GitHub runs it best effort: measured with the Actions API (event=schedule), the last 8 scheduled runs on master, 2026-10-18 12:11Z to 2026-10-19 13:50Z, were 2.1 to 7.5 hours apart.Docs only, three edits: the two sentences now name the cron as best effort, and a short "How often it runs" section gives the measured gaps and says pushes to master and
workflow_dispatchare the dependable triggers. A faster heartbeat (an external dispatch) is a separate decision and is not part of this PR.The em dashes that
grepshows in the README predate this change.🤖 Generated with Claude Code