-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using GitHub Actions to automate update monitor & contribution #2
Comments
Thanks for the suggestions! Now in terms of manual work, I actually have a bit of python that I still haven't added to the repo that does most things already: I simply add something to the .js file (this is the single source of truth), and the script resorts the js and regenerates the README.md. The script also goes and fetches all the last updated timestamps from GitHub, this is not manual either. If I understand your suggestion correctly it sounds like the tool I'm mentioning would be 90% of what the action would need to do. Interesting. |
I can help with this as I've actually made quite a lot actions before. Could you put your script into this repo? |
I'd appreciate the help with the action. I'll add the script to the repo after I get it de-hackified a bit which might be another week given how July has gone so far. I'll ping the issue once it's there. |
Better Workflow for this repo
Automated Contribution
This repo is actually using GitHub as an DB. Now, if one wants to contribute to this repo, he has to modify the README.md & data.js (which is even sorted, have to find correct place to insert new plugin).
That's quite compilcated. We can actually use GitHub Actions:
In this way we can make the "DB" insertion more friendly
Automated Update Check
Secondly, the last update time is still manually measured. Considered that most plugins are hosted on github, we can actually make a cron gitthub action to automatically check all plugin's update time.
The updater then automatically updates README and data.js, which release repo owner from updating everything manually
The text was updated successfully, but these errors were encountered: