style: prettier (#2624)

docs/recipes/ci-configurations/README.md

@@ -1,4 +1,5 @@
 # CI configurations
+
 - [CircleCI 2.0 workflows](circleci-workflows.md)
 - [Travis CI](travis.md)
 - [GitLab CI](gitlab-ci.md)

docs/recipes/ci-configurations/github-actions.md

@@ -35,7 +35,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v2
         with:
-          node-version: 'lts/*'
+          node-version: "lts/*"
       - name: Install dependencies
         run: npm ci
       - name: Release
@@ -64,9 +64,11 @@ If the risk is acceptable, some extra configuration is needed. The [actions/chec
 ## Trigger semantic-release on demand
 
 ### Using GUI:
+
 You can use [Manual Triggers](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/) for GitHub Actions.
 
 ### Using HTTP:
+
 Use [`repository_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#repository_dispatch) event to have control on when to generate a release by making an HTTP request, e.g.:
 
 ```yaml
@@ -85,7 +87,8 @@ $ curl -v -H "Accept: application/vnd.github.everest-preview+json" -H "Authoriza
 ```
 
 ### Using 3rd party apps:
+
 If you'd like to use a GitHub app to manage this instead of creating a personal access token, you could consider using a project like:
 
-* [Actions Panel](https://www.actionspanel.app/) - A declaratively configured way for triggering GitHub Actions
-* [Action Button](https://github-action-button.web.app/#details) - A simple badge based mechanism for triggering GitHub Actions
+- [Actions Panel](https://www.actionspanel.app/) - A declaratively configured way for triggering GitHub Actions
+- [Action Button](https://github-action-button.web.app/#details) - A simple badge based mechanism for triggering GitHub Actions

docs/recipes/ci-configurations/gitlab-ci.md

@@ -21,8 +21,8 @@ This example is a minimal configuration for **semantic-release** with a build ru
 ```yaml
 # The release pipeline will run only if all jobs in the test pipeline are successful
 stages:
-    - test
-    - release
+  - test
+  - release
 
 before_script:
   - npm install
@@ -52,7 +52,6 @@ This example is a minimal configuration for **semantic-release** with a build ru
 
 **Note**: The`semantic-release` execution command varies depending if you are using a [local](../../usage/installation.md#local-installation) or [global](../../usage/installation.md#global-installation) **semantic-release** installation.
 
-
 ```yaml
 # The release pipeline will run only on the master branch a commit is triggered
 stages: