-
Notifications
You must be signed in to change notification settings - Fork 674
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
Cleanup of stale issues #8685
Cleanup of stale issues #8685
Conversation
# You can adjust the behavior by modifying this file. | ||
# For more information, see: | ||
# https://github.com/actions/stale | ||
name: Mark stale issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the name accurate? isn't it "Close stale issues"?
only-labels: code-vs-markup-mismatch | ||
exempt-issue-labels: 'feature proposal' | ||
exempt-all-milestones: true | ||
debug-only: ${{ github.event_name == 'pull_request' }} # Dry-run changes to the workflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does this mean? only CI and release pipelines would execute?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, the 'on' is only allowing pull request and manual. I commented it out to be 100% sure that it doesn't run on every pull request change in the repo.
/azp run |
No commit pushedDate could be found for PR 8685 in repo microsoft/microsoft-ui-xaml |
Do you have an ETA for when the internal issues will be made public? And is the commitment to make GitHub the source going forward? |
The cleanup is complete. Closing, since this was a one-time effort. |
Description
This adds a manual-only workflow that is being used for the actual cleanup.
Motivation and Context
As we mentioned in the last community call, we are moving away from the model that tracked issues separately in github and AzureDevOps and towards a single list of issue that includes both. This will involve bringing all active github issues internally. To do this, we can’t (and shouldn’t) drown ourselves in the significant backlog that we have allowed to grow in github (mea culpa!).
What this means is that we will be bulk closing any issue that has not seen any activity in the last 180 days. We will be creating an exception for Feature Requests, and handling those separately.
If you have issues that you still care deeply about that have been lying dormant, all you need to do is post a single comment. That will set the Last Activity Date as today, and the issue will remain as-is. After any item is closed, it (of course) may be reopened.
Our logic here is that 180 days takes us back to the release of WinAppSDK 1.2. Please attempt to repro any older bugs on a recent build and update the results.