Configure an Improvement Job

Before you configure a job

Choose one repository and one published improvement. Confirm that repository access is healthy and read the paired audit or improvement description. A schedule authorizes future eligibility within that runbook’s scope; it does not authorize work on a different repository or broaden what the runbook may change.

Some jobs need a prior audit candidate. If no relevant audit has run yet, Guard can schedule the required audit bootstrap before it has fixable evidence.

Choose the write behavior

The provider issue is the baseline artifact for supported Autofix jobs. Turn off Open a pull request with the fix for issue-only behavior: Guard can create or reuse an issue, but it must not edit files, create a branch, or open a pull or merge request. Turn the option on to permit an issue plus a review request when the candidate passes the runbook’s safety and verification gates.

The toggle is permission to attempt the bounded path, not a guarantee that every run creates code. Duplicate work, stale evidence, unsafe scope, and failed verification can still produce issue-only or no-write outcomes. Humans always review and merge.

Choose frequency and time

Available frequencies include daily, workdays, three times a week, twice a week, weekly, and monthly. Weekly patterns allow preferred weekdays. Choose the displayed run time and verify the timezone. The schedule system can distribute work to avoid unnecessary collisions, so treat the configured value as scheduling intent rather than a real-time execution promise.

Use a cadence that leaves reviewers enough time to resolve existing artifacts. More frequent runs are not useful when issues and review requests are accumulating faster than the team can process them.

Enable or run once

Saving an enabled job creates or updates its recurring schedule. Run now is a separate manual action and does not require the recurring switch to stay on. Use it when you want one current attempt without committing to repeated work.

Recent runs show whether work is in progress and link to available reports or artifacts. A schedule can be turned off without deleting its completed history.

Verify the configuration

Check that the card shows the expected repository, improvement, on/off state, frequency, selected days, time, timezone, and write behavior. After the first run, confirm that its report reflects those choices and that provider links target the correct repository.

If the job repeatedly creates work nobody reviews, use Manage the Autofix backlog and pauses before increasing frequency.