Add a GitHub Action to close issues with outdated versions#3652
Add a GitHub Action to close issues with outdated versions#3652ryanlua wants to merge 13 commits intobloxstraplabs:mainfrom
Conversation
Add a workflow for checking issue versions
|
Feel free to test out how it works by creating an issue in https://github.com/RyanLua/bloxstrap/issues where it is live and where the PR is merging from. @pizzaboxer mentioned about extending my initial feature request issue (#3513 (comment)) for auto respond to keywords but this PR is not for that. |
|
I was considering writing my own action application to handle this, I didn't think about (or even know that you could use) action scripting. This is really nice, thanks. I will definitely need to make adjustments to this though. |
Yeah, definitely let me know what changes you need or just directly edit this PR. I guessed some generic comments responses. As mentioned previously, you can update the PR to add in a auto responder to key words since the code is fairly easy to edit to add that functionality. |
|
Nice idea! Wishes the best for #3652! |
I think you should handle different variations, such as |
That is a good idea. I'll go work on adding version format variations. |
|
bump! @bluepilledgreat |
|
This is such a good idea, why is this stale... |
|
this will get merged tomorrow trust |
Creates a GitHub Action workflow that runs every time a bug report issue is created to check the Bloxstrap version in the Bloxstrap version field and whether it is the latest version.
If
### Bloxstrap Versionexists in the issue body and it cannot detect the version, it will comment the below (and not close the issue):If it properly detects the Bloxstrap version and it is outdated, it will comment the below and close the issue as not planned:
The workflow derives the latest Bloxstrap version from the
<Version>key in theBloxstrap/Bloxstrap.csprojfile.Closes #3513