-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Add a GitHub Action to close issues with outdated versions #3652
base: main
Are you sure you want to change the base?
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. |
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 Version
exists 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.csproj
file.Closes #3513