Adding option to varying body text length used for matching #3
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
…t contains log files, etc. The premise is that the start of the body has the most pertinent content. This PR makes it configurable by adding a --body-length parameter. It defaults to -1 which means whole body
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Some repositories may achieve better results by varying the length of body text used for matching.
This is especially useful when longer body text in some issues contains information such as logs that may affect similarity.
The idea is that the most relevant content is typically found at the beginning of the body. To make this feature more customizable, a --body-length parameter has been added to this PR. By default, it is set to -1, which means that the entire body will be considered.