[BUGFIX][DEV-1630] Convert tags to branch names for specific repositories #129
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
andreaskienast
force-pushed
the
bugfix/DEV-1630
branch
from
e4b1177
to
8e5b316
Compare
NeoBlack
previously approved these changes
Aug 15, 2023
andreaskienast
force-pushed
the
bugfix/DEV-1630
branch
from
8e5b316
to
6f5b688
Compare
…ries When registering documentation renderings, extension manuals must follow specific rules, means that only tags are accepted. However, there's an exception for some repositories where only branches are allowed. This collides with the "tag only" rule and leads to an unresolvable situation. The validation is now adapted for special repositories that tries to derive the branch name from the tag name and uses this result instead.
andreaskienast
force-pushed
the
bugfix/DEV-1630
branch
from
6f5b688
to
144349e
Compare
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.
When registering documentation renderings, extension manuals must follow specific rules, means that only tags are accepted. However, there's an exception for some repositories where only branches are allowed. This collides with the "tag only" rule and leads to an unsolvable situation.
The validation is now adapted for special repositories that tries to derive the branch name from the tag name and uses this result instead.