Stale issue un-assignment isn't working 🙃

[camelPhonso]

Description of the Bug

If an issue is assigned with the request command it will not be properly unassigned when it's gone stale for more than 7 days.

What should happen instead

When the issue receives a comment saying it it's been stale for too long the user should be unassigned from it

Steps to reproduce this bug

1. request an issue
2. don't complete it
3. receive a warning that the issue is stale, and finally a confirmation that you are being removed
4. the issue is still assigned

What could we do to solve this bug?

This is happening because the label that tracks issues assigned via automation is also set as the pin_label which prevents unassignment.

This might have been part of a previous system to manage unassignment when issues need to be in review for a long time but we now have the in review label, so that should be the new pin_label instead

Assignment

I'd like to work on this Issue myself

[github-actions[bot]]

🤖 meep morp!

Thank you for your contribution camelPhonso!! 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:

• common Patterns we follow in the code base
• conventions set for commit messages and naming functions, classes or files

💡 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 ! 🦆