@@ -225,7 +225,7 @@ Badges are generated with [anybadge](https://pypi.org/project/anybadge/) by the
The drawback of this approach is, that one a single Artifacts section is allowed in .gitlab-ce.yml. And this needs to be 'pages' in this case. All CI Jobs must share the same Artifacts.
The artifact "pages" is published online by [GitLab Pages](https://docs.gitlab.com/ee/user/project/pages/). Therefore, for all CI Jobs a fixed URL is available to the latest generated badge.
An example URL is: {{{http://vis.pages.jsc.fz-juelich.de/jusense-cicd/badges/badge_build-openmpi_%{default_branch}.svg}}}
An example URL is: `http://vis.pages.jsc.fz-juelich.de/jusense-cicd/badges/badge_build-openmpi_%{default_branch}.svg`
##### Badges based on data from GitLab-API
Certain informations on your project are available through the [GitLab-API](https://docs.gitlab.com/ee/api/README.html). With 'curl' one can ask GitLab for information and it will pass a JSON file. You can get the number of forks for example with
