Automatic unassign for stale issues

[Azanul]

Added 2 github actions:

1. Labels all issues inactive for 14 days as "stale"
2. Unassigns an issue whenever it is labeled as "stale"

[welcome]

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

• Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
• Sign off your commits (Reference: DCO Guide).

[Azanul]

@samhita-alla Check it out and let me know if I've missed anything.

[samhita-alla]

Are you sure this works?

[samhita-alla]

@Azanul where is {{ github.event.issue.assignee }} documented in GitHub docs? I want to make sure this works.

[samhita-alla]

@Azanul, can you work on my suggestions so that I can merge this PR?

[Azanul]

@samhita-alla go to https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
check the entry for github.event , it says:-

This object is identical to the webhook payload of the event that triggered the workflow run, and is different for each event.

Now checkout the webhook payload of issues event.

[samhita-alla]

@Azanul, thanks! Will this work if there are multiple assignees?

[Azanul]

@Azanul, thanks! Will this work if there are multiple assignees?

For handling multiple assignees, I'll have to use issues.assignees and fetch login value of each object to put in the array. I reckoned from here that you might not want handling of multiple assignees, so I didn't do it.

[samhita-alla]

Oh, I meant I don't want to block assigning an issue to multiple people. But if we're going to unassign after the issue goes stale, unassigning all of them makes sense, right?

[Azanul]

Oh, I meant I don't want to block assigning an issue to multiple people. But if we're going to unassign after the issue goes stale, unassigning all of them makes sense, right?

Done, for multiple assignees