feat(automerge): restrict auto-merge to configured days of the week
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 2
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 17
Description
Summary
Add a config option to limit auto-merge to specific days of the week, so teams can align dependency merges with their release cadence and avoid merging right before train pushes or the weekend.
Motivation
On mozilla/fxa we push to prod on a train schedule. We'd like Dependabot updates to auto-merge only on days when someone is around to watch them land — e.g. Mon and Thu, skipping Tue/Wed (train pushes) and Fri + weekend. Today auto-merge runs on the ~30-min sweep with no day/time controls, so a safe-but-unwatched merge can land at an awkward moment.
Proposed behavior
- New optional config under
automerge, e.g.:automerge: allowed_days: [mon, thu] # empty/unset = all days (current behavior) timezone: America/Los_Angeles # days evaluated in this tz; default UTC - When
allowed_daysis set, a PR that passes all existing auto-merge checks is only merged if the current day (intimezone) is in the list. Otherwise it's held and re-evaluated on the next eligible day's sweep. - Unset/empty
allowed_dayspreserves today's behavior exactly. - Configurable per-repo via
.blender/blender.yml, falling back toconfig/defaults.yml.
Notes / open questions
- Day evaluated at merge time (sweep tick), not PR-open time — is that the expected semantics?
- Worth a companion
allowed_hourswindow later, but out of scope here unless trivial. - BLEnder's comment on a held PR should say why it's waiting and when it'll retry (ties into the spirit of #67).
Docs
Update README.md auto-merge section (and any config reference) to document allowed_days / timezone in the same PR.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the auto-merge sweep and configuration flow, then inspect config/defaults.yml and the per-repository .blender/blender.yml location. Update README.md's auto-merge section and config reference; done means eligible merges respect allowed_days and timezone, held PRs retry on eligible sweeps, and unset or empty settings preserve current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100