edvm
diff --git a/‎docs/tutorials/github_actions.md
Lines changed: 13 additions & 27 deletions b/‎docs/tutorials/github_actions.md
Lines changed: 13 additions & 27 deletions
diff --git a/‎docs/tutorials/gitlab_ci.md
Lines changed: 10 additions & 10 deletions b/‎docs/tutorials/gitlab_ci.md
Lines changed: 10 additions & 10 deletions
@@ -16,38 +16,24 @@ name: Bump version
 on:
   push:
     branches:
-      - master  # another branch could be specified here
+      - master
 
 jobs:
-  build:
+  bump-version:
     if: "!startsWith(github.event.head_commit.message, 'bump:')"
     runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        python-version: ['3.x']
+    name: "Bump version and create changelog with commitizen"
     steps:
-    - uses: actions/checkout@v2
-      with:
-        token: '${{ secrets.PERSONAL_ACCESS_TOKEN }}'
-        fetch-depth: 0
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v1
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python --version
-        python -m pip install -U commitizen
-    - name: Create bump
-      run: |
-        git config --local user.email "action@github.com"
-        git config --local user.name "GitHub Action"
-        cz bump --yes
-    - name: Push changes
-      uses: Woile/github-push-action@master
-      with:
-        github_token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
-        tags: "true"
+      - name: Check out
+        uses: actions/checkout@v2
+        with:
+          token: '${{ secrets.PERSONAL_ACCESS_TOKEN }}'
+          fetch-depth: 0
+      - name: Create bump and changelog
+        uses: commitizen-tools/commitizen-action@master
+        with:
+          github_token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
+
 ```
 
 Push to master and that's it.
 
@@ -1,18 +1,18 @@
-### Create a new release using GitLab CI
+## Create a new release using GitLab CI
 
 For this example, we have a `python/django` application and `Docker` as a containerization tool.
 
-*Goal*: Bump a new version every time that a change occurs on the `master` branch. The bump should be executed automatically by the `CI` process.
+_Goal_: Bump a new version every time that a change occurs on the `master` branch. The bump should be executed automatically by the `CI` process.
 
-#### Development Workflow:
+### Development Workflow
 
 1. A developer creates a new commit on any branch (except `master`)
 2. A developer creates a merge request (MR) against `master` branch
 3. When the `MR` is merged into master, the 2 stages of the CI are executed
 4. For simplification, we store the software version in a file called `VERSION`. You can use any file that you want as `commitizen` supports it.
 5. The commit message executed automatically by the `CI` must include `[skip-ci]` in the message; otherwise, the process will generate a loop. You can define the message structure in [commitizen](https://commitizen-tools.github.io/commitizen/bump/) as well.
 
-#### Gitlab Configuration:
+### Gitlab Configuration
 
 To be able to change files and push new changes with `Gitlab CI` runners, we need to have a `ssh` key and configure a git user.
 
@@ -40,15 +40,15 @@ If you have more projects under the same organization, you can reuse the deploy
 
 tip: If the CI raise some errors, try to unprotected the private key.
 
-#### Defining GitLab CI Pipeline
+### Defining GitLab CI Pipeline
 
 1. Create a `.gitlab-ci.yaml` file that contains `stages` and `jobs` configurations. You can find more info [here](https://docs.gitlab.com/ee/ci/quick_start/).
 
 2. Define `stages` and `jobs`. For this example, we define two `stages` with one `job` each one.
-    * Test the application.
-    * Auto bump the version. This means changing the file/s that reflects the version, creating a new commit and git tag.
+   - Test the application.
+   - Auto bump the version. This means changing the file/s that reflects the version, creating a new commit and git tag.
 
-#### Stages and Jobs
+### Stages and Jobs
 
 ```yaml
 image: docker:latest
@@ -76,7 +76,7 @@ auto-bump:
   stage: auto-bump
   image: python:3.6
   before_script:
-    - 'which ssh-agent || ( apt-get update -qy && apt-get install openssh-client -qqy )'
+    - "which ssh-agent || ( apt-get update -qy && apt-get install openssh-client -qqy )"
     - eval `ssh-agent -s`
     - echo "${SSH_PRIVATE_KEY}" | tr -d '\r' | ssh-add - > /dev/null # add ssh key
     - pip3 install -U Commitizen # install commitizen
@@ -102,7 +102,7 @@ auto-bump:
       - master
   artifacts:
     paths:
-    - variables
+      - variables
 ```
 
 So, every time that a developer push to any branch, the `test` job is executed. If the branch is `master` and the test jobs success, the `auto-bump` takes place.