Skip to content

README: running a Pickup run on a schedule - #299

Merged
JacobStephens2 merged 2 commits into
issue-212from
issue-287
Oct 1, 2026
Merged

JacobStephens2 merged 2 commits into
issue-212from
issue-287

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Summary

Closes #287

 README.md
 ## Pickup runs
   ### The Claim limit
   ### The Sweep
   ### Why an issue was passed over
   ### One Run notification for the issue taken
+  ### A Pickup run on a schedule     # the crontab entry, and what differs from an Architect run's

 thirdshift help
   pickup … Run notification
+  To run a Pickup run on a schedule … the README's "A Pickup run on a schedule" has a crontab entry.

The new section holds the crontab entry and the no-merge variant, and points to the Architect run's "On a schedule" for PATH, the logins and other schedulers. It then says what is a Pickup run's own:

  • the interval, one issue a pass, and where the Claim limit stops it;
  • one line per repository, and the lock shared with an Architect run;
  • the three skips, exit 0, no email, and what the log file holds;
  • a failed issue keeps its Claim, and thirdshift <Issue URL> sends it round again by hand;
  • the warning for the upstream to-spec and to-tickets.

Evidence

  • Before: help_points_to_running_a_pickup_run_on_a_schedule_without_the_recipe fails: help lacks "To run a Pickup run on a schedule, …".
    After: it passes, and cargo fmt --check, cargo clippy --all-targets -- -D warnings and cargo test are clean: 30 test binaries, 0 failed.

The prose was checked against src/pickup.rs, src/claim.rs and fn pickup in src/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

  • Duplicated Code, README: the opening sentence, the 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.
  • Duplicated Code, test: the new help test copies its Architect neighbour's shape. Skipped: the file keeps one self-contained mention-list test per help topic, and a helper for two callers would hide the strings each asserts.

Spec

  • Not asked for: the "A Run notification" bullet. Kept: it follows from "a skip sends no email", and says a quiet inbox doesn't show the passes are running.
  • Not asked for: the sentence on base <branch> in the Pickup runs section. Kept, reworded so it no longer says base is required to schedule a pass: it is the one link from the flag to the new section.
  • Not asked for: a new test. Kept: it holds the criterion that help points to the schedule without repeating the recipe.

Merge Danger

Door: two-way

Prose and one help paragraph; reverting the commits undoes it.

Blast Radius: docs

thirdshift help grows by two lines, which also follow every argument error on stderr.

🤖 Generated with Claude Code

JacobStephens2 and others added 2 commits October 1, 2026 20:32
… 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>
@JacobStephens2
JacobStephens2 merged commit 1f0a937 into issue-212 Oct 1, 2026
13 checks passed
@JacobStephens2
JacobStephens2 deleted the issue-287 branch October 1, 2026 20:51
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.

1 participant