[DO NOT MERGE] Create stale_issues.yaml #5366
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dry run for adding an action that would comment on very old issues and apply the awaiting-feedback label. (see [Automate comments on stale issues](https://docs.google.com/document/d/1UCGvPZ9m7vHpl5E6jIt8PUV7J6SVGOf-wMHrB4OfBt0/edit?tab=t.0#heading=h.vmiybe9heukw), [Stale Issues Proposal](https://docs.google.com/document/d/1dw7ehY3kchsyEO_M5z9vcpleHNEzwpTdl2G-8UnmpKQ/edit?tab=t.0))
mjeffryes
commented
Mar 21, 2025
mjeffryes
commented
Mar 21, 2025
mjeffryes
commented
Mar 21, 2025
mjeffryes
commented
Mar 21, 2025
mjeffryes
commented
Mar 21, 2025
mjeffryes
commented
Mar 21, 2025
mjeffryes
changed the title
Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5366 +/- ##
=======================================
Coverage 24.31% 24.31%
=======================================
Files 364 364
Lines 145577 145577
=======================================
Hits 35401 35401
Misses 110077 110077
Partials 99 99 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this pull request
Jul 23, 2025
We've discussed this a few times, but never quite pulled the trigger. This picks up the last PR: [[DO NOT MERGE] Create stale_issues.yaml · pulumi-aws/5366](pulumi/pulumi-aws#5366) which tested this workflow against AWS. For this PR, I've kept the logic identical to that test, just moving it to ci-mgmt and running it on a cron: The action is configured to look for kind/bug issues that have not been updated in the last and have fewer than 2 upvotes. It would comment on these issues with the text: > Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still experiencing this issue, could you leave a quick comment to let us know so we can prioritize it? and add the awaiting-feedback label. If a non-pulumi user replies, the issue will be bumped back into the triage queue using the usual automation. If no one replies, these issues will eventually show up in our "stale awaiting feedback" query on the team dashboards so we can take one last look at them and decide if we should close them. The workflow defaults to just doing a dry run and I've added a new config flag to turn off dryRun and comment/label the issues for real. (So we can roll this out gradually to provider repos or disable it for a single repo if needed.)
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this pull request
Jul 23, 2025
We've discussed this a few times, but never quite pulled the trigger. This picks up the last PR: [[DO NOT MERGE] Create stale_issues.yaml · pulumi-aws/5366](pulumi/pulumi-aws#5366) which tested this workflow against AWS. For this PR, I've kept the logic identical to that test, just moving it to ci-mgmt and running it on a cron: The action is configured to look for kind/bug issues that have not been updated in the last and have fewer than 2 upvotes. It would comment on these issues with the text: > Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still experiencing this issue, could you leave a quick comment to let us know so we can prioritize it? and add the awaiting-feedback label. If a non-pulumi user replies, the issue will be bumped back into the triage queue using the usual automation. If no one replies, these issues will eventually show up in our "stale awaiting feedback" query on the team dashboards so we can take one last look at them and decide if we should close them. The workflow defaults to just doing a dry run and I've added a new config flag to turn off dryRun and comment/label the issues for real. (So we can roll this out gradually to provider repos or disable it for a single repo if needed.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dry run for adding an action that would comment on very old issues and apply the awaiting-feedback label. (see Automate comments on stale issues, Stale Issues Proposal)
The action is configured to look for
kind/bugissues that have not been updated in the last and have fewer than 2 upvotes. It would comment on these issues with the text:and add the
awaiting-feedbacklabel. If a non-pulumi user replies, the issue will be bumped back into the triage queue using the usual automation. If no one replies, these issues will eventually show up in our "stale awaiting feedback" query on the team dashboards so we can take one last look at them and decide if we should close them.