GitHub Action - Automatic unassignment of stale issues

[palisadoes]

Is your feature request related to a problem? Please describe.

1. A lot of time is spent by volunteers unassigning issues that have the no-issue-activity label by our stale.yml GitHub Action.
2. This process needs to be automated.

Describe the solution you'd like

1. A GitHub Action that does the following:

   1. Checks the current repository, and if it is not archived then:
      1. Identifies open issues that have the no-issue-activity label
      2. Identifies whether the the issue has an OPEN linked pull request:
         1. in the same repository being linked to the issue.
         2. authored by the assignee of the issue.
      3. Identifies whether the issue has an assignee
      4. If all these criteria are found to be true: 1. After a configured grace period in days:
         2. Unassign the issue
         3. Leave a pre-configured message in the issue comment addressing the user who has been unassigned.

2. The GitHub action will eventually reside in the PalisadoesFoundation/.github repository and be used centrally by all repositories. The action will need to take this into account.

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• See above

Additional context

• N/A

[Ritesh-251]

/assign

[palisadoes-bot]

❌ @Ritesh-251 First time contributors cannot use auto assignment. You have not successfully merged code into this repository. Please ask to be assigned instead.

[Ritesh-251]

@palisadoes pls assign the issue here and lets test it

[palisadoes]

You are going to have to test this with issues using minutes or seconds for the timeout

[Ritesh-251]

ok sir

[Ritesh-251]

@palisadoes i need a little guidance
i tested it in my talawa-admin fork [

] and it is working as expected.. was this the validation you were looking for, or maybe i got it wrong .

[palisadoes]

@Ritesh-251

There was no requirement for a report.

The GitHub action needs to unassign people where the issue has:

1. the no-issue-activity label
2. no open PRs linked to it assigned to the assignee
3. exceeded the timeout period.

The issue description is clear:

• GitHub Action - Automatic unassignment of stale issues #24 (comment)

Let me understand the concern.

[Ritesh-251]

You are going to have to test this with issues using minutes or seconds for the timeout

@palisadoes can you clarify a bit
i am not able to understand this .. did you meant- It should support very small timeout values so that its behavior can be validated quickly ..
i am confused beacuse in the issue it is written After a configured grace period in days:

[palisadoes]

1. Yes, eventually it will be set to a number of days, but that could be in seconds.
2. You will need to set the time out in seconds in order to test. For example, you create an issue and assign the label, you don't want to wait a day to be able to test it. Ideally you'd want a timeout of 5 minutes.

[palisadoes]

Practice with this on a new repo in your GitHub account. Then when ready try it here, then we can move it across all the repos.