Skip to content

Update branch naming in git documentation#1793

Merged
lzybkr merged 1 commit into
PowerShell:masterfrom
vors:branch-naming-1
Aug 13, 2016
Merged

Update branch naming in git documentation#1793
lzybkr merged 1 commit into
PowerShell:masterfrom
vors:branch-naming-1

Conversation

@vors
Copy link
Copy Markdown
Collaborator

@vors vors commented Aug 13, 2016

Remove statement about using "alias/feature-name"

Remove statement about using "alias/feature-name"
@rkeithhill
Copy link
Copy Markdown
Collaborator

Just out of curiosity, why remove this? On the projects I work on, they use username/topic-name for private user branches (bug fixes, feature impls) and feature-name for shared feature branches. This makes it easy to identify a dev's private branch from shared feature branches. The / character also results in a nice, tree-view display in Visual Studio's Branches tool window. :-)

@vors
Copy link
Copy Markdown
Collaborator Author

vors commented Aug 13, 2016

We don't plan to use the main repo for private dev branches. Devs are working from their forks (mostly). Current guidelines could still be applied, but since fork name already provides a moniker, it's not that important.

@rkeithhill
Copy link
Copy Markdown
Collaborator

Ah yeah, that makes sense. Thanks.

@lzybkr lzybkr merged commit a652f52 into PowerShell:master Aug 13, 2016
@lzybkr lzybkr deleted the branch-naming-1 branch August 13, 2016 22:25
JamesWTruher referenced this pull request in JamesWTruher/PowerShell Aug 17, 2016
Remove statement about using "alias/feature-name"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants