Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FabricBot] Add 'possibly-stale' GH label for closing old issues. #7343

Merged
merged 1 commit into from
Sep 6, 2022

Conversation

jpobst
Copy link
Contributor

@jpobst jpobst commented Sep 6, 2022

Copy https://github.com/dotnet/runtime automation for backlog-cleanup-candidate as possibly-stale.

When we place the issue label possibly-stale on an issue, it will kick off the following workflow:

  • A comment will be added to the issue that states:
We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 
14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
  • If anyone comments on the issue during this timespan, the possibly-stale label will be removed and the need-attention label will be applied so we can review the comment.
  • If no one comments on the issue during this timespan, the issue will be closed with the comment:
This issue will now be closed since it had been marked `possibly-stale` but received no further activity in 
the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will 
be locked if it remains inactive for another 30 days.

Copy link
Member

@jonathanpeppers jonathanpeppers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the idea is we put possibly-stale manually to start this process?

@jpobst
Copy link
Contributor Author

jpobst commented Sep 6, 2022

Yes, dotnet/runtime also automatically kicks off the process after 5 years of inactivity, but I'm not a huge fan of automatically closing old issues. So we can start with this and see how it goes.

@jonpryor jonpryor merged commit 3918337 into main Sep 6, 2022
@jonpryor jonpryor deleted the possibly-stale branch September 6, 2022 20:54
grendello added a commit to grendello/xamarin-android that referenced this pull request Sep 6, 2022
* main:
  [FabricBot] Add `possibly-stale` GitHub label for closing old issues (dotnet#7343)
  Don't use Dictionary<K,V> to avoid duplicate value exception (dotnet#7340)
  [One .NET] fix `dotnet run -c Release` (dotnet#7341)
grendello added a commit to grendello/xamarin-android that referenced this pull request Sep 6, 2022
* mm-runtime:
  [FabricBot] Add `possibly-stale` GitHub label for closing old issues (dotnet#7343)
  Don't use Dictionary<K,V> to avoid duplicate value exception (dotnet#7340)
  [One .NET] fix `dotnet run -c Release` (dotnet#7341)
grendello added a commit to grendello/xamarin-android that referenced this pull request Sep 6, 2022
* mm-cleanup-and-enable:
  [FabricBot] Add `possibly-stale` GitHub label for closing old issues (dotnet#7343)
  Don't use Dictionary<K,V> to avoid duplicate value exception (dotnet#7340)
  [One .NET] fix `dotnet run -c Release` (dotnet#7341)
  Make AOT work (with trimming)
  Fix Debug mode and Release w/o marshal methods
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants