See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
Git worktree it a git feature which allows you to checkout a single repository into multiple locations on your filesystem. It has a few rough edges, but if you follow a few simple rules it can be make context switching much easier than git's other mechanisms, such as stashing or switching branches. My folder structure will usually look something like this:
MyRepo/
master/ ← The original checkout, using something like git clone <repo url> master
brew install azure-cliaz extension add --name azure-devopsbrew install azure-cliaz extension add --name azure-devopsAlso known as the User Story. Explain the requirement in a sentence or two. This should just enough text to identify the requirement, including any crucial information about site/environment.
As a [user role], I want [function], so that [value].
If this doesn't fit as a user story (e.g., a bug ticket), that's fine, just explain it as a concise sentence.
| 1. You mast have a public key from your mashine stored on github as SSH key here: | |
| https://github.com/settings/ssh | |
| How to create ssh key on unix/mac os x: | |
| - Open terminal, go to the root typing: $ cd ~ (recommended) | |
| - Type: ssh-keygen -t rsa -C "your@email.address" | |
| - To secure your ssh key ststem will ask you for passphrase (recommended) but you can skip it also | |
| - That's you have the ssh key | |
| - Check it with: $ ls -al ~/.ssh |