Automate `lake update` PRs
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 709
- Forks
- 200
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 45
Description
Following #293, we would like a workflow that automates running lake update. What I would like ideally is:
- at some cron interval (day, week?) the bot runs
lake updateand opens a PR - if CI is a success, the bot places it on the merge queue
- on failure, the PR remains open so a maintainer can fix
This will need to be a little different from the Mathlib equivalent, as the bot will need to actually merge the PR versus leaving a bors comment.
Contributor guide
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 by reading issue #293 and the Mathlib equivalent mentioned in the issue to understand the existing update workflow. Inspect the repository's current CI and workflow configuration, then determine how lake update, PR creation, CI results, and merge-queue handling should fit together. Done means a scheduled update PR is opened, merged after successful CI, and left open on failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100