Skip to content

Place the managed cron block first - #462

Merged
cgraf78 merged 1 commit into
mainfrom
cron-managed-first
Nov 4, 2026
Merged

cgraf78 merged 1 commit into
mainfrom
cron-managed-first

Conversation

@cgraf78

@cgraf78 cgraf78 commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Summary

Place the managed cron block first so its shell, environment and path also apply to later unmanaged jobs. Later unmanaged assignments continue to override earlier values for subsequent jobs.

  • Relocate existing bottom-positioned blocks even when their contents are unchanged and report misplaced blocks in doctor.
  • Refuse ambiguous markers and re-read the crontab before rewriting; the crontab interface still has no atomic compare-and-swap.
  • Document that formerly preceding unmanaged assignments no longer configure managed jobs after migration.

Testing

  • dot test (38 suites passed, one skip; an earlier unrelated prompt test failure did not reproduce in isolation or on the full rerun)
  • dot test core-cron core-doctor (passed)
  • checkrun format and checkrun lint (passed)
  • ShellCheck inventory and git diff --check (passed)
  • Personal cron fragment integration against the staged base (42 assertions passed)

Review

Independent review covered malformed and duplicate markers, migration, idempotence, doctor alignment, concurrent edits and effects on unmanaged jobs.

Summary

Apply the managed cron environment to all following jobs by placing its
  block at the start of the crontab.

- relocate unchanged legacy blocks and report misplaced blocks in doctor
- reject ambiguous markers and recheck the crontab before rewriting it
- preserve later unmanaged assignments as explicit overrides

Testing

- dot test (38 suites passed, one skipped)
- dot test core-cron core-doctor
- checkrun format and checkrun lint
- ShellCheck inventory and git diff --check
@cgraf78
cgraf78 merged commit 9a3a7be into main Nov 4, 2026
41 of 43 checks passed
@cgraf78
cgraf78 deleted the cron-managed-first branch November 4, 2026 16:37
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