fix: wrong prepare comment when default creation trigger used #71
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.
Type of Change
Description
As can be seen in this prepare comment the device spec is added even the default create comment (without
android
orios
) was used here. The wrong part of the prepare comment is the following:This shouldn't be there for the default create comment. More precisely,
os
andcategory
are completely wrong.The root cause of the bug is that the
CREATE_COMMENT_PREFIX
we use in the implementation to split up the creation comment contained a trailing space. Thus, wrong data was extracted. This fix removes the trailing space.Checklist