-
Notifications
You must be signed in to change notification settings - Fork 825
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
GitHub action for stale issues #3075
Conversation
Build Failed 😱 Build Id: 2c7b6319-4bf5-4547-9f62-b3fb85f25f60 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 3c1bc031-ccd6-4234-a577-63f928b9e349 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geetachavan1, markmandel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Will this workflow close the existing open issues which do not have activity for more than 90 days? Looking at the issue queue, most of them do not have activity for 90 days, my concern is the workflow should not close them silently without us triaging first. |
@gongmax The workflow will close only the ones that carry 'obsolete' label and to gain 'obsolete' label first it needs to get the 'stale' label. SO the short answer is NO.. No issues will be closed silently |
Great! |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 675c2b5a-ffb8-4bdf-a1ae-145ed3f11ab7 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
* Create stale.yaml * Create obsolete.yaml * Create close.yaml * Update close.yaml * Update obsolete.yaml * Update stale.yaml
What type of PR is this?
What this PR does / Why we need it:
Which issue(s) this PR fixes:
Closes #
Special notes for your reviewer:
If approved and merged, for the successful run we will need to create following labels