/ eslint Public
chore: Set up automatic updating of README #16717
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.
What is the purpose of this pull request? (put an "X" next to an item)
[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
The sponsors data in the README hasn't been updated since we switched over to the new website. We were previously running the README update from the old website repo.
This PR updates the script to fetch data from the new eslint.org repo and also adds a workflow that goes off each night (after the website update) to check for new data.
Additionally, I've run the script once to update the current README.
Is there anything you'd like reviewers to focus on?
I created a new npm script called "build:readme". Based on our current conventions it seemed like that was the most appropriate, but please let me know if it should be named something else.