New round of updates

Closes #3439644

docs/info/common.md

@@ -33,11 +33,11 @@ Alternatively, you can also use the `before_script` with the `--no-update` flag
     - composer require --dev predis/predis --no-update
 ```
 
-## Including a non-required module for testing.
+## Including a non-required module for testing
 
 Add the module to the `require-dev` section of your module's `composer.json` file. It will be installed only when requested by developers and the CI process.
 
-## Install Javascript libraries.
+## Install Javascript libraries
 
 If packages cannot be installed via `composer` or `yarn`, you can still download them directly.
 
@@ -138,6 +138,11 @@ Most environment variables are created when the pipeline is first built, but the
   - !reference [ .create-environment-variables ]
 ```
 
+## Adding a pipeline status badge
+
+Gitlab provides automatic images of the status of pipelines. You can add this to your project's readme.md file to give a quick visual indication of the state when browsing the repository.
+The details are on https://docs.gitlab.com/ee/user/project/badges.html
+
 ## Running pipelines via the GitLab UI
 
 You can run pipelines from the GitLab UI by navigating to: `Build` > `Pipelines` > `Run pipeline`. When you do this, all the variables inherited from the templates will be presented in the form and you can override any value. These changes will take priority over any pre-defined value or value set in the `.gitlab-ci.yml` file.