This repository has been archived by the owner on Dec 9, 2022. It is now read-only.
Let the label bot respond to additional comments; not just when an issue is created #72
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
…sue is opened. * See kubeflow/code-intelligence#133 we want to allow the label bot to respond after additional comments on an issue and take those comments into account. This is because additional comments on the issue might provide more data pointing at how the issue should be labeled. * We only do this for issues that are forwarded to a pubsub backend and using the newer code for label prediction. related to kubeflow/code-intelligence#133
jlewi
changed the title
|
/lgtm |
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.
…sue is opened.
See [label bot] Use text in additional comments not just the initial comment kubeflow/code-intelligence#133 we want to allow the label bot
to respond after additional comments on an issue and take those comments
into account. This is because additional comments on the issue
might provide more data pointing at how the issue should be labeled.
We only do this for issues that are forwarded to a pubsub backend and
using the newer code for label prediction.
related to kubeflow/code-intelligence#133