Skip to content

Removed incorrect GitHub tag name translation explanation#14360

Merged
v-regandowner merged 1 commit intoMicrosoftDocs:mainfrom
thisisthekap:patch-2
Apr 16, 2026
Merged

Removed incorrect GitHub tag name translation explanation#14360
v-regandowner merged 1 commit intoMicrosoftDocs:mainfrom
thisisthekap:patch-2

Conversation

@thisisthekap
Copy link
Copy Markdown
Contributor

For GitHub Tags, hyphens are not getting replaced by underscores in Build.SourceBranchName.

This change reflects this behavior in the docs.

For GitHub Tags, hyphens are not getting replaced by underscores in Build.SourceBranchName.

This change reflects this behavior in the docs.
@prmerger-automator
Copy link
Copy Markdown
Contributor

@thisisthekap : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Azure Pipelines variable documentation to accurately reflect how Build.SourceBranchName is populated for Git tags (specifically, that hyphens in tag names are preserved rather than translated).

Changes:

  • Corrects the Build.SourceBranchName example for refs/tags/... to keep hyphens (your-tag-name) instead of showing underscores (your_tag_name).

@ttorble
Copy link
Copy Markdown
Contributor

ttorble commented Mar 4, 2026

@juliakm

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@juliakm
Copy link
Copy Markdown
Collaborator

juliakm commented Apr 16, 2026

Thanks for your contribution!

#sign-off

@v-regandowner v-regandowner merged commit ac6a626 into MicrosoftDocs:main Apr 16, 2026
6 checks passed
@thisisthekap thisisthekap deleted the patch-2 branch April 16, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants