[ci] update issue-locking workflow #6256
Merged
Conversation
This file contains 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
jameslamb
requested review from
guolinke,
shiyu1994,
jmoralez and
borchero
as code owners
jmoralez
approved these changes
Jan 3, 2024
|
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposes a few changes to the GitHub Actions workflow we use to close issues and labels:
v5ofdessant/lock-threadsWhy now?
@dessant, the author of
lock-threads, tagged me to tell me that extra double quotes are no longer necessary: dessant/lock-threads#40 (comment).Why increase the time-til-locking?
I've found that locking a PR / issue prevents GitHub from generating these annotations showing that the PR / issue was mentioned somewhere else.
I've found those annotations really useful, for example to discover problems in other projects that were caused by changes here.
I'd like to extend the time-til-locking so that we can see more of those annotations in the time after a release.