Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support release branches based on the forward slash separator #8903

Merged
merged 2 commits into from Feb 19, 2019

Conversation

TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Feb 16, 2019

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

Copy link
Contributor

@RDIL RDIL left a comment

Choose a reason for hiding this comment

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

Looks good, just think this should be 1 word

.github/ISSUE_TEMPLATE/Release_Process.md Outdated Show resolved Hide resolved
Co-Authored-By: TravisEz13 <travis.plunk@microsoft.com>
@TravisEz13 TravisEz13 merged commit af4e811 into PowerShell:master Feb 19, 2019
@TravisEz13 TravisEz13 deleted the add_suppot_for_forward_slash branch February 19, 2019 18:47
@adityapatwardhan adityapatwardhan added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Feb 19, 2019
TravisEz13 added a commit to TravisEz13/PowerShell that referenced this pull request May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants