Description
Configuration Change:
The GitHub Actions workflow that is used in this repo, .github/workflows/update-best-of-list.yml is from the [best-of(https://github.com/best-of-lists/best-of) project, which also contains the template from which new best-of lists, like this one, can be generated. It copies the original update-best-of-list.yml, from here. It uses the best-of-update-action, which in turn uses the Python code from the best-of-generator package to turn a projects.yaml into a README.md.
The best-of project has been updated recently (2024), but not the other components, which are actually used for updating this list. The original update-best-of-list.yml in the template has not been updated since 2022, the action since 2022, and the generator even since 2021.
In #345, I created personal forks of the latter two, for debugging purposes only.
- https://github.com/Irratzo/best-of-lists_best-of-update-action
- https://github.com/Irratzo/best-of-lists_best-of-generator
In this project, the switch to use either the official or the personal fork action, is here (permalink).
If the official projects being unmaintained, the likelihood that they will break at some point increases. Or if major configuration changes are undertaken for this list. In that case, the procedure done in #345 can be adapted for that.
This issue for listing possible current or future concerns that advocate for switching to such a self-maintained version of the update-cation and the best-of-generator.