Fixing branch name logic. #3989
Merged
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
Member
StephenBonikowsky
commented
Oct 23, 2019
StephenBonikowsky
commented
- The existing logic didn't account for a branch name being "release/3.1.0"
- We leveraged the azure devops variable 'Build.SourceBranchName' which returned the "last path segment in the ref string".
* The existing logic didn't account for a branch name being "release/3.1.0" * We leveraged the azure devops variable 'Build.SourceBranchName' which returned the "last path segment in the ref string".
StephenBonikowsky
force-pushed
the
stebon/3.1.0/infraupdates
branch
from
9dda2f2 to
bb026c2
Compare
|
Need to merge in order to trigger the CI build to validate these changes. |
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.