For any pull request with the 'community' label:
1. After 21 days of inactivity: give a warning that the pull request is out of date and will be closed.
2. After 28 days of inactivity: close the pull request.
Only check once a week (every Monday - there's no hurry here), so there may be
an additional 6 days until the inactivity workflow is triggered (if the last
action occurred on a Tuesday)
Unanswered question: I'm not sure if the first action will be considered as
some activity, in which case the second action will only happen in 21 + 28
days = 49 days. It doesn't really matter; the important part is that pull
requests are automatically closed after some time (and 49 days - even 55 days
- is still way better than now, which can be years).
Currently a descriptive comment is automatically added to an issue when either
the 'need-info' or the 'need-repro' label is added to an issue, requesting
more info or a test project, respectively, and then when the reporter (or
anyone else) comments something, the `need-info`/`need-repro` label is removed
and a `need-attention` label is added.
However, sometimes this can get repetitive if the reporter replies frequently,
or someone else steps in and answers questions or asks unrelated questions,
and we have to add back the `need-info` or `need-repro` every time.
So add an opt-out: if the label `no-auto-reply` is set, then don't add that
descriptive comment.
The label is single-use: it'll be removed when a `need-info` or `need-repro`
labels is added.
Add prIssueManagement.yml to onboard repo to GitOps.ResourceManagement
as FabricBot replacement
Owners of the FabricBot configuration should have received email
notification. The same information contained in the email is published
internally at: https://aka.ms/gim/fabricbot. Details on the replacement
service and the syntax of the new yaml configuration file is available
publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html
Rolf Bjarne Kvinge
microsoft-github-policy-service[bot]