feat: use more explicite names for templates

README.md

@@ -10,12 +10,12 @@
 include:
   - project: "open-source/gitlab-templates"
     ref: "branch/default"
-    file:                                       # the stages are:
-      - "templates/no-duplicate-pipelines.yml"  # use workflow to avoid duplicated pipelines
-      - "templates/docker-build.yml"            # build a docker image
-      - "templates/build-debian.yml"            # will build a .deb and upload it to heptapod
-      - "templates/release-on-heptapod.yml"     # this will create a release on heptapod AND uses uploaded .deb by build-debian
-      - "templates/publish-pypi.yml"            # this will release on pypi using "tox -e pypi-publish"
+    file:                                           # the stages are:
+      - "templates/no-duplicated-ci-pipelines.yml"  # use workflow to avoid duplicated pipelines
+      - "templates/build-docker-image.yml"
+      - "templates/build-debian-package.yml"        # will build a .deb and upload it to heptapod
+      - "templates/create-release-on-heptapod-including-debian-package.yml"
+      - "templates/upload-to-pypi.yml"
 ```
 
 Depending on your templates you will need certains stages **in a specific order**:
@@ -23,5 +23,5 @@
 ```yaml
 stages:
   # put your testing/linting stages here before
-  # for build-debian.yml
+  # for build-debian-package.yml
   - build-debian
@@ -27,5 +27,5 @@
   - build-debian
-  - upload-deb
-  # for docker-build.yml
+  - upload-deb-to-heptapod
+  # for build-docker-image.yml
   # for release-on-heptapod.yml
   - release
@@ -30,6 +30,6 @@
   # for release-on-heptapod.yml
   - release
-  # for publish-pypi.yml
+  # for upload-to-pypi.yml
   - publish
 ```
 
@@ -39,12 +39,12 @@
 include:
   - project: "open-source/gitlab-templates"
     ref: "branch/default"
-    file:                                       # the stages are:
-      - "templates/no-duplicate-pipelines.yml"  # use workflow to avoid duplicated pipelines
-      - "templates/build-debian.yml"            # will build a .deb and upload it to heptapod
-      - "templates/release-on-heptapod.yml"     # this will create a release on heptapod AND uses uploaded .deb by build-debian
-      - "templates/publish-pypi.yml"            # this will release on pypi using "tox -e pypi-publish"
+    file:                                           # the stages are:
+      - "templates/no-duplicated-ci-pipelines.yml"  # use workflow to avoid duplicated pipelines
+      - "templates/build-debian-package.yml"        # will build a .deb and upload it to heptapod
+      - "templates/create-release-on-heptapod-including-debian-package.yml"
+      - "templates/upload-to-pypi.yml"
 
 stages:
   - lint
   - test
@@ -47,9 +47,9 @@
 
 stages:
   - lint
   - test
-  - build-debian
-  - upload-deb
+  - build-debian-package
+  - upload-deb-to-heptapod
   - release
   - publish
 ```

templates/build-debian.yml → templates/build-debian-package.yml

@@ -4,7 +4,7 @@
 
 
 build-debian:
-  stage: build-debian
+  stage: build-debian-package
   image: logilab/cubicweb:buster-buildpackage
   rules:
     - if: '$CI_MERGE_REQUEST_ID'
@@ -20,7 +20,7 @@
       - repo
 
 upload-deb-to-heptapod:
-  stage: upload-deb
+  stage: upload-deb-to-heptapod
   image: curlimages/curl:latest
   rules:
     - if: '$CI_MERGE_REQUEST_ID'