Replies: 1 comment 4 replies
-
|
@lalvarezt I'm all up for this! |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently there's no way to know, for a plugin, when was the last change done and to which version/tag/commit we're aligned to.
I started playing with some ideas in here
The overall workflow is here
Ignore the code part that looks like AI slop, this was just a quick prototype to evaluate options
It will look something like this:
The general idea is that we would have some scripts (and a GH workflow) to detect changes upstream (either tagged releases or pure commits) and show badges on the potential drift that we might want to have a look.
Note: In order to make badges work and to avoid churn on the readme page I experimented with Github Pages (I tried Wiki but couldn't make it work for some reason). This way when a change is detected the readme itself doesn't change because the badge is taken from the GH Pages
The GH Pages look like this, and gives a quick way of showing the diff for the changes for quick inspection
Beta Was this translation helpful? Give feedback.
All reactions