Support release branches based on the forward slash separator#8903
Merged
TravisEz13 merged 2 commits intoPowerShell:masterfrom Feb 19, 2019
Merged
Support release branches based on the forward slash separator#8903TravisEz13 merged 2 commits intoPowerShell:masterfrom
TravisEz13 merged 2 commits intoPowerShell:masterfrom
Conversation
iSazonov
approved these changes
Feb 17, 2019
RDIL
approved these changes
Feb 18, 2019
Contributor
RDIL
left a comment
There was a problem hiding this comment.
Looks good, just think this should be 1 word
Co-Authored-By: TravisEz13 <travis.plunk@microsoft.com>
adityapatwardhan
approved these changes
Feb 19, 2019
TravisEz13
added a commit
to TravisEz13/PowerShell
that referenced
this pull request
May 14, 2019
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
PR Summary
Support release branches based on the forward slash separator
PR Context
This format of branches allows us to create branch policies (Setup CI) in Azure Dev Ops once, rather than for each branch.
See
https://beeming.net/vsts-tfs/2018/3/setting-wild-card-branch-policies-in-vsts
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.[feature]to your commit messages if the change is significant or affects feature tests