The main issue is needing to set up a PR to see if CI passes. This takes time as docker needs to spin up and do each step each run (including repository setup alongside install dependencies). A task runner would allow any contributor to run (common) tests and checks before creating a PR. A contributor would also only need to task run relevant tasks, not all of them.
This would also improve development experience since you do not need to run the relevant checks manually (think building, tests, lint check, etc.). This is especially good as a final check before committing or before setting up a pull request.
Lastly, a task runner can also be used to do the build & install in a single command, which is a nice addition.
How should it work
We can use various options. Options include GNU make (wikipedia page since their website seems inaccesible), lefthook, redo, and fastbuild. Make seems like the best option as we probably all have it installed already. I will leave it up to you to assess what is best.
Other approaches considered
No response
Area
CI / Tooling
Mockups / references / notes
No response
### What's missing / annoying
The main issue is needing to set up a PR to see if CI passes. This takes time as docker needs to spin up and do each step each run (including repository setup alongside install dependencies). A task runner would allow any contributor to run (common) tests and checks before creating a PR. A contributor would also only need to task run relevant tasks, not all of them.
This would also improve development experience since you do not need to run the relevant checks manually (think building, tests, lint check, etc.). This is especially good as a final check before committing or before setting up a pull request.
Lastly, a task runner can also be used to do the build & install in a single command, which is a nice addition.
### How should it work
We can use various options. Options include [GNU make](https://en.wikipedia.org/wiki/Make_(software)) (wikipedia page since their website seems inaccesible), [lefthook](https://github.com/evilmartians/lefthook), [redo](https://github.com/apenwarr/redo), and [fastbuild](https://github.com/fastbuild/fastbuild). Make seems like the best option as we probably all have it installed already. I will leave it up to you to assess what is best.
### Other approaches considered
_No response_
### Area
CI / Tooling
### Mockups / references / notes
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What's missing / annoying
The main issue is needing to set up a PR to see if CI passes. This takes time as docker needs to spin up and do each step each run (including repository setup alongside install dependencies). A task runner would allow any contributor to run (common) tests and checks before creating a PR. A contributor would also only need to task run relevant tasks, not all of them.
This would also improve development experience since you do not need to run the relevant checks manually (think building, tests, lint check, etc.). This is especially good as a final check before committing or before setting up a pull request.
Lastly, a task runner can also be used to do the build & install in a single command, which is a nice addition.
How should it work
We can use various options. Options include GNU make (wikipedia page since their website seems inaccesible), lefthook, redo, and fastbuild. Make seems like the best option as we probably all have it installed already. I will leave it up to you to assess what is best.
Other approaches considered
No response
Area
CI / Tooling
Mockups / references / notes
No response