Weekly CI job to update Manifest and post a PR
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 238
- Forks
- 107
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 2
Description
Every time I write new docs or update stuff, I run into weird stuff happening with deps, whether it's SciML stuff or ForwardDiff 1.0 or just other weird things. This time (#676), it's the Core Functionality page which broke, which is a bit ironic.
I think it would make sense to have a weekly cron job that runs Pkg.update() in the top level dir and makes a PR with any changes to Manifest.toml, then at least we can separate the task of writing docs from the task of keeping up to date with dependency churn.
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 inspecting the repository's CI configuration and the top-level Manifest.toml, then trace how Julia package updates are currently run. Done means a weekly job runs Pkg.update(), changes Manifest.toml when needed, and opens a pull request containing those changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100