Repository navigation
README: running a Pickup run on a schedule - #299
Merged
Merged
Conversation
… to it in thirdshift help Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… which skips have passed-over lines, the Base branch for a retry by hand, the skills by name Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 1, 2026
Merged
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.
Summary
Closes #287
The new section holds the crontab entry and the
no-mergevariant, and points to the Architect run's "On a schedule" forPATH, the logins and other schedulers. It then says what is a Pickup run's own:0, no email, and what the log file holds;thirdshift <Issue URL>sends it round again by hand;to-specandto-tickets.Evidence
help_points_to_running_a_pickup_run_on_a_schedule_without_the_recipefails:help lacks "To run a Pickup run on a schedule, …".After: it passes, and
cargo fmt --check,cargo clippy --all-targets -- -D warningsandcargo testare clean: 30 test binaries, 0 failed.The prose was checked against
src/pickup.rs,src/claim.rsandfn pickupinsrc/main.rs, and by the Spec review. The crontab entry itself was not run: no agent or CI can, so it needs a person to try it on a Linux machine with cron.Unaddressed findings
Standards
PATH=line and the flags paragraph repeat the Architect run's "On a schedule". Skipped: README: running a Pickup run on a schedule #287 asks for a complete entry to paste, and the rest already points to that section.Spec
base <branch>in the Pickup runs section. Kept, reworded so it no longer saysbaseis required to schedule a pass: it is the one link from the flag to the new section.Merge Danger
Door: two-way
Prose and one help paragraph; reverting the commits undoes it.
Blast Radius: docs
thirdshift helpgrows by two lines, which also follow every argument error on stderr.🤖 Generated with Claude Code