adapt warnings-ng plugin to new versioning tagging #257
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
bmunozm
force-pushed
the
update-warnings-ng-tag
branch
from
3a04a23
to
3053f7b
Compare
raul-arabaolaza
approved these changes
Sep 24, 2020
|
Build fail is unrelated and the test have been run successfully, merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Until version 8.4.1 the versioning of the plugin is
warnings-ng-${version}, and after it, it is usedv${version}This PR is making the warnings-ng plugin PCT will be able to launch against all versions