- Git In Visual Studio
- Visual Studio Git Plugin 2015
- Visual Studio Git Plugin 2019
- Visual Studio Git Plugin 2019
- Visual Studio Git Plugin Ssh
Install above vscode (version >=1.42.0) and The git plugin needs to be installed.
- Git, installed Visual Studio Code, installed A basic understanding of Git concepts and commands, such as working with repositories, forks, clones, and branches, staging and unstaging changes, and pushing commits. You need a GitHub account.
- To set Git as a default source control plug-in for the new solution in Visual Studio 2017, you should do the following: Open Tool Menue Options. At Source Control Plug-in Selection Make sure that the Git.
Follow the Angular Team Commit Specification,like the following:
Type
Using GitHub with Visual Studio Code lets you share your source code and collaborate with others. GitHub integration is provided through the GitHub Pull Requests and Issues extension. Install the GitHub Pull Requests and Issues extension.
Must be one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing or correcting existing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Scope
The scope could be anything specifying place of the commit change. For example $location
, $browser
, $compile
, $rootScope
, ngHref
, ngClick
, ngView
, etc...
You can use *
when the change affects more than a single scope.
Subject
The subject contains succinct description of the change:
- use the imperative, present tense: 'change' not 'changed' nor 'changes'
- don't capitalize first letter
- no dot (.) at the end
Body
Just as in the subject, use the imperative, present tense: 'change' not 'changed' nor 'changes'. The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit closes.
Breaking Changes should start with the word BREAKING CHANGE:
with a space or two newlines. The rest of the commit message is then used for this.
Git In Visual Studio
A detailed explanation can be found in this document.
Quick start
Visual Studio Git Plugin 2015
Step1 Install the plugin
Step2 Use the command shortcut
showGitCommit
to open the command window or Click the icon on the git plugin navigation barStep3 Enter the commit information, which automatically generates a commit message that conforms to the specification
Settings Options
GitCommitPlugin.ShowEmoji
: whether to show emoji, defaulttrue
.
Visual Studio Git Plugin 2019
GitCommitPlugin.CustomCommitType
: customize the commit type, defaultnull
.
GitCommitPlugin.MaxSubjectWords
: customize the maximum number of words on the subject, default20
.