Merge branch 'master' into feature/fix-git-section-redirections

Author: cesiztel

.env.dist

@@ -0,0 +1 @@
+GH_TOKEN=

.gitignore

@@ -13,4 +13,6 @@ _book
 # eBook build output
 *.epub
 *.mobi
-*.pdf
+*.pdf
+
+.env

README.md

@@ -12,6 +12,7 @@ We accept recommendations from all enthusiastic who care about the quality. The
 * [Git](../git/)
 * [Java](../java/)
 * [PHP](../php/)
+* [Python](../python/)
 * [VueJS](../vuejs/)
 
 ## Contributions

SUMMARY.md

@@ -15,6 +15,7 @@
   * [Branch Naming](git/branch-naming.md)
   * [Commit Message Naming](git/commit-message-naming.md)
   * [Pull Request Naming](git/pull-request-naming.md)
+  * [Tag Naming](git/tag-naming.md)
 * [Java](java/README.md)
   * [Class Naming](java/class-naming.md)
   * [Interface Naming](java/interface-naming.md)
@@ -37,4 +38,14 @@
   * [Templates components Naming](vuejs/templates-components-naming.md)
   * [Constants naming](vuejs/constants-naming.md)
   * [Method Naming](vuejs/method-naming.md)
-  * [Variable Naming](vuejs/variable-naming.md)
+  * [Variable Naming](vuejs/variable-naming.md)
+* [Python](python/README.md)
+  * [Class Naming](python/class-naming.md)
+  * [Module Naming](python/module-naming.md)
+  * [Method Naming](python/method-naming.md)
+  * [Variable Naming](python/variable-naming.md)
+  * [Constant Naming](python/constant-naming.md)
+  * [Package Naming](python/file-naming.md)
+  * [Exception( Error ) Naming](python/exception-naming.md)
+  * [Underscore](python/underscore.md)
+

_layouts/website/page.html

@@ -109,5 +109,16 @@
         });
       }
       </script>
+
+      <!-- Global site tag (gtag.js) - Google Analytics -->
+      <script async src="https://www.googletagmanager.com/gtag/js?id=UA-138722543-1"></script>
+      <script>
+        window.dataLayer = window.dataLayer || [];
+        function gtag(){dataLayer.push(arguments);}
+        gtag('js', new Date());
+
+        gtag('config', 'UA-138722543-1');
+      </script>
+
 </div>
 {% endblock %}

book.json

@@ -4,7 +4,9 @@
     "github-edit",
     "sitemap-general",
     "smart-nav-collapse",
-    "githubcontributors"
+    "githubcontributors",
+    "link-fix",
+    "contributors-each-page"
   ],
   "pluginsConfig": {
     "github-edit": {
@@ -18,6 +20,12 @@
       "githubOwner": "naming-convention",
       "githubRepository": "naming-convention-guides",
       "contributorWidth": "40px"
+    },
+    "contributors-each-page": {
+      "owner": "naming-convention",
+      "repository": "naming-convention-guides",
+      "title": "Contributors",
+      "excluded": ["README.md"]
     }
   },
   "styles": {

docs/CONTRIBUTING.md

@@ -34,7 +34,7 @@ Please follow recommended workflow below:
 1. Please fork this repo and send pull requests.
 2. For minor edits, you edit pages using Github's web-based editor.
 3. For major edits, it will be better to make a pull request or use [gitbook-editor](https://legacy.gitbook.com/editor) on localhost.
-4. It will be useful to check [gitbook help docs](http://help.gitbook.io/). Not all docs may be useful to you.
+4. It will be useful to check [gitbook help docs](https://help.gitbook.com/). Not all docs may be useful to you.
 
 Please feel free to open a [github issue](https://github.com/wpveda/book/issues) if you need more help.
 
@@ -50,4 +50,4 @@ Please feel free to open a [github issue](https://github.com/wpveda/book/issues)
 **Gitbook Editor**
 
 1. For offline editing - desktop tool gitbook editor can be used - [https://legacy.gitbook.com/editor/releases](https://legacy.gitbook.com/editor/releases)
-2. Once you download Gitbook editor, open the repo folder from your forked & locally cloned git repo.
+2. Once you download Gitbook editor, open the repo folder from your forked & locally cloned git repo.

git/README.md

@@ -1,13 +1,8 @@
 # Git Naming Convention
 List of covered sections:
 * [Branch Naming](../git/branch-naming.md)
-<<<<<<< Updated upstream
-* [Commit Message Naming](../java/commit-message-naming.md)
-* [Pull Request Naming](../java/pull-request-naming.md)
-=======
 * [Commit Message Naming](../git/commit-message-naming.md)
 * [Pull Request Naming](../git/pull-request-naming.md)
 * [Tag Naming](../git/tag-naming.md)
->>>>>>> Stashed changes
 
 Missing something? Please contribute here by reading [this guide](../docs/CONTRIBUTING.md).

git/commit-message-naming.md

@@ -26,4 +26,17 @@ Example:
 Implement proper authorization for each service on development phase to validate during the API call.
 
 Access right management is used to check proper authorization to access an API by an employee or the employer.
-```
+```
+
+## Conventional Commits
+
+Commit messages **MAY** use [Conventional Commits](https://www.conventionalcommits.org/en/) format. It provides guidelines to create a better commit history log, making easier to have automated tasks around it (e.g. automated changelogs). Commits would follow the format `<type>[optional scope]: <description>`, where `<type>` might be `feat`/`fix`/`chore`/`docs` etc. and breaking changes are indicated on the beginning of the optional body or footer section. 
+
+Example:
+```
+git commit -m "feat(survey): add nps survey to the home page
+
+BREAKING CHANGE:  `survey` objects in xml file have been re-used in the global configurations.
+```
+
+Please refer to [Conventional Commits docs](https://www.conventionalcommits.org/en/) for more details

git/tag-naming.md

@@ -0,0 +1,14 @@
+# Git Naming Convention > Tag Naming
+
+May:
+- Use [Semantic Versioning](https://semver.org/)
+- Prefix the version number with the letter *v*
+
+Suggested Formats:   
+- With prefix *{vX.Y.Z}*
+- Without prefix *{X.Y.Z}*
+
+Example:
+```git
+git tag -a 1.0.2 // or optionally v1.0.2
+```