[x] My code follows the style guidelines of this project
[x] I have performed a self-review on my code
[x] I have made corresponding changes to the documentation (if any were needed)
[x] My changes generate no new warnings or errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and previously existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
Description
Closes #171
Added an automated workflow that will alert us when an issue or pull request has been left inactive for too long. Issues will be deleted after 7 days of being left stale but prs will not. Combining this with the automated workflows in our project board should help the core team keep a close eye on issues and prs if any become redundant or are left unanswered for too long.
I order to 'refresh' a stale issue or pr all that's needed is that a user becomes active on it by either commenting, reviewing or pushing new code.
Files changed
created .github/workflows/stale.yml file to automate the workflow
added @actions/github dependency
UI changes
No UI changes 🙅
Changes to Documentation
No new documentation needed as this will run in the background
Tests
This PR does not affect the behaviour of the code and did not require writing new tests. HOWEVER, the workflow has been tested with the act command on the terminal.
You will need to have docker installed and run the command act -s GITHUB_KEY=secrets.GITHUB_KEY to simulate the github action in a container. You can view an update on each step of the action and the final result in your terminal.
Checklist:
Description
Closes #171
Added an automated workflow that will alert us when an issue or pull request has been left inactive for too long. Issues will be deleted after 7 days of being left stale but prs will not. Combining this with the automated workflows in our project board should help the core team keep a close eye on issues and prs if any become redundant or are left unanswered for too long.
I order to 'refresh' a stale issue or pr all that's needed is that a user becomes active on it by either commenting, reviewing or pushing new code.
Files changed
.github/workflows/stale.yml
file to automate the workflow@actions/github
dependencyUI changes
No UI changes 🙅
Changes to Documentation
No new documentation needed as this will run in the background
Tests
This PR does not affect the behaviour of the code and did not require writing new tests. HOWEVER, the workflow has been tested with the
act
command on the terminal.You will need to have docker installed and run the command
act -s GITHUB_KEY=secrets.GITHUB_KEY
to simulate the github action in a container. You can view an update on each step of the action and the final result in your terminal.