-
Notifications
You must be signed in to change notification settings - Fork 543
Add machine-readable dates to keep docs up-to-date #1018
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I suggested one way of doing it here: #1013 (comment) Another way is to use HTML comments like |
We decided in today's meeting that we should do this with a GitHub action that runs monthly and opens at most one issue with checkboxes for each section of the guide that's out of date (and preferably tag it with E-easy). |
Status update: I've been working on this, and I think it's almost done! 🎉 I also had an idea for a way to make sure people use
where |
Yeah, I think it's better if new things are added to GitHub — plus it's easier since it seems GitHub Actions would have better integrations with GitHub, e.g. for opening issues ;) |
I tested this on a private repo, and confirmed that it works! 🎉 PR: #1037 |
Since it's February 3, and thus we missed the start of the month, and also to test it, I'm going to manually trigger a run of the date-checker now! |
It worked! #1046 |
Is there someway to make the data references machine parseable? We could then write a simple tool to remind us when references are ~6 months old, and we should check it they’re still true.
Originally posted by @rylev in #1013 (comment)
The text was updated successfully, but these errors were encountered: