Closed mnixo closed 1 month ago
🤖 meep morp!
Thank you for your contribution mnixo!! This Issue has been assigned to you as requested ✨
🔎 Please keep in mind that in order to give everyone a chance to contribute Issues may be unassigned if they go stale. You will be warned if the Issue is marked as stale at any point.
🔎 Please review our documentation for guidance on:
💡 The core team is available for any help and will try to respond to any comments in this Issue or questions on discord as quickly as possible.
Happy coding ! 🦆
@camelPhonso, I'm seeing that the workflow has already ran successfully, but looking at the logs:
Run boundfoxstudios/action-unassign-contributor-after-days-of-inactivity@v1.0.2
Found 4 issues to process...
Unassigning issue #291...
Unassigning issue #268...
Unassigning issue #254...
I'm seeing that the action picked up on these issues and added a message, but they are still assigned. To be fair, some of them are still pretty active nonetheless, but the point is that the action doesn't seem to be working as expected. Please review.
Description of the Bug
The Auto Unassign Inactive Issues GitHub Actions workflow is not working currently. Each run is hanging with the following message for 40+ hours:
What should happen instead
Fix the workflow so that it doesn't hang and runs as expected.
Steps to reproduce this bug
Go to the Actions tab and pick the Auto Unassign Inactive Issues workflow. See this example of a workflow run.
What could we do to solve this bug?
No response
Assignment
I'd like to work on this Issue myself