Consider using autofix.ci in PRs
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 106
- Forks
- 223
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 72
Description
We could use autofix.ci to automatically fix pull requests that just need ./fix running on them. This would save writer/developer time as they won't need to do it manually.
It could also save CI time if we have the other CI checks depend on the autofix job completing first; I regularly push commits then have to push a follow-up lint commit, which means CI runs twice, which is wasteful.
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 by inspecting the repository's existing pull-request CI checks and the ./fix entry point. Compare how autofix.ci could run ./fix and how the other checks could depend on that job. Done means applicable pull requests are fixed automatically and redundant CI runs are avoided.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100