Update chapter-06-gbapp-reference.md
This commit is contained in:
parent
d5e493b0ae
commit
6cb5c8da42
1 changed files with 19 additions and 1 deletions
|
@ -223,7 +223,25 @@ This in some way contributes to a better understanding of how it works.
|
||||||
|
|
||||||
1. Visit https://<SITENAME>.scm.azurewebsites.net/api/vfs/LogFiles/Application/index.html
|
1. Visit https://<SITENAME>.scm.azurewebsites.net/api/vfs/LogFiles/Application/index.html
|
||||||
|
|
||||||
|
## Commit code
|
||||||
|
|
||||||
|
Numbering:
|
||||||
|
|
||||||
|
1.0.0
|
||||||
|
MAJOR.MINOR.PATCH
|
||||||
|
BREAK.FEATURE.BUG
|
||||||
|
|
||||||
|
Rules:
|
||||||
|
|
||||||
|
If the body contains the text “BREAKING CHANGE” then MAJOR version is incremented.
|
||||||
|
If the type contains feat/feature, then MINOR version is incremented.
|
||||||
|
If the type contains fix, then PATCH version is incremented.
|
||||||
|
And finally, if the type contains refactor/style/perf/doc/test/chore, then nothing is increment and no release is made.
|
||||||
|
|
||||||
|
|
||||||
|
Source: https://medium.com/agoda-engineering/automating-versioning-and-releases-using-semantic-release-6ed355ede742
|
||||||
|
|
||||||
|
|
||||||
## Tooling
|
## Tooling
|
||||||
|
|
||||||
### JavaScript
|
### JavaScript
|
||||||
|
|
Loading…
Add table
Reference in a new issue