Skip to content
Snippets Groups Projects
Select Git revision
  • testing protected
  • 375-add-an-api-endpoint-for-user-creation
  • 341-ci-interdire-les-nombres-dans-le-scope-des-messages-de-commit
  • dev default protected
  • master protected
  • 213-husky-must-be-disabled-for-ci
  • test/dad-pipeline
  • release/4.3.2 protected
  • release/4.3.1 protected
  • release/4.3.0-testing.9 protected
  • release/4.3.0 protected
  • release/4.3.0-testing.8 protected
  • release/4.2.6 protected
  • release/4.3.0-testing.7 protected
  • release/4.3.0-testing.6 protected
  • release/4.3.0-testing.5 protected
  • release/4.3.0-testing.4 protected
  • release/4.3.0-testing.3 protected
  • release/4.3.0-testing.2 protected
  • release/4.3.0-testing.1 protected
  • release/4.2.5 protected
  • release/4.2.4 protected
  • release/4.2.3 protected
  • release/4.2.2 protected
  • release/4.2.1 protected
  • release/4.2.0 protected
  • release/4.2.0-testing.4 protected
27 results
Blame Permalink
Forked from apps.education / laboite
Source project has a limited visibility.
  • Daniel Dehennin's avatar
    abde698d
    ci(commitlint): enforce commit message format · abde698d
    Daniel Dehennin authored 
    We want to generate release automatically when the `stable` branch is
pushed.

We will use `semantic-release` to do the jobs and we must make sure
the commits will be taken into account by the automatic process.

* doc/CONTRIBUTING.md: explain the commit message formatting

* .gitlab-ci.yml: include the `commitlint` jobs from EOLE/ci-tools>
    abde698d
    History
    ci(commitlint): enforce commit message format
    Daniel Dehennin authored 
    We want to generate release automatically when the `stable` branch is
pushed.

We will use `semantic-release` to do the jobs and we must make sure
the commits will be taken into account by the automatic process.

* doc/CONTRIBUTING.md: explain the commit message formatting

* .gitlab-ci.yml: include the `commitlint` jobs from EOLE/ci-tools>