-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
add more bots #2843
Merged
add more bots #2843
Changes from 3 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
5e47d3a
Create release-drafter.yml
guolinke 2e748b6
Create no-response.yml
guolinke d207f31
disable comments
guolinke 085011e
Apply suggestions from code review
guolinke dc7d0fd
Update release-drafter.yml
guolinke 6500836
Apply suggestions from code review
guolinke 0095be0
Update .vsts-ci.yml
guolinke File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# Configuration for probot-no-response - https://github.com/probot/no-response | ||
|
||
# Number of days of inactivity before an Issue is closed for lack of response | ||
daysUntilClose: 14 | ||
guolinke marked this conversation as resolved.
Show resolved
Hide resolved
|
||
# Label requiring a response | ||
responseRequiredLabel: awaiting response | ||
# Comment to post when closing an Issue for lack of response. Set to `false` to disable | ||
closeComment: false | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we please add a closeComment: >
This issue has been automatically closed because it has been awaiting a response for too long.
When you have time to to work with the maintainers to resolve this issue, please post a new comment and it will be re-opened.
If the issue has been locked for editing by the time you return to it, please open a new issue and reference this one. Thank you for taking the time to improve LightGBM!
guolinke marked this conversation as resolved.
Show resolved
Hide resolved
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
name-template: v$NEXT_PATCH_VERSION | ||
tag-template: v$NEXT_PATCH_VERSION | ||
categories: | ||
- title: 🚀 Features | ||
label: feature | ||
- title: 🐛 Bug Fixes | ||
label: fix | ||
- title: 🧰 Maintenance | ||
label: chore | ||
tag-template: - $TITLE @$AUTHOR (#$NUMBER) | ||
template: | | ||
## Changes | ||
|
||
$CHANGES |
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.
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.
@guolinke
Sorry, haven't had a chance to read about bots yet. But at present I'm personally trying to give from 25 to 30 days for providing any feedback after the last ping. Maybe we can increase this value for at least 21 days?..
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.
^ I agree with this. I think 21 or even 30 days would be better. I think the main goal of the bot should be to automate some of the work we do to clean up things that are months old