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

Naming of commands #51

Open
lw-schick opened this issue Nov 9, 2016 · 2 comments
Open

Naming of commands #51

lw-schick opened this issue Nov 9, 2016 · 2 comments
Assignees

Comments

@lw-schick
Copy link

Can we rename all the commands with the prefix "Git"?
f.e.:

Get-GitBranch instead of Get-Branch - or -
New-GitRemote instead of New-Remote?

I think that is more like the PowerShell naming standard. When you take a look at the module SQLPS, you will find out that next to all commands are using Sql as the prefix.

@czhang03
Copy link

Also I personally think private function like

Function        GitConvertColor                                    2.0.4      PSGit
Function        GitWriteMessage                                    2.0.4      PSGit

should not be exported.

@Jaykul
Copy link
Member

Jaykul commented Feb 17, 2017

The commands are prefixed by the psd1, and the private functions are supposed to be blocked by it, but aren't right now!

The idea was that FunctionsToExport should be set to "*-*" not to "*" ... thus preventing the private functions from being exported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants