implement gitlab-ci-cli package

I remove issue template because he is not quite suitable for request.

It is will be great have package for gitlab CI, i spend around 2 hours for searching right configuration, but don’t find any information and use workaround:

node_modules/.bin/commitlint --from=HEAD~$(git --no-pager rev-list master..HEAD --count)

I don’t known about right usage this. Please correct me if this is not a very good solution.

Link to gitlab CI environment variables: https://docs.gitlab.com/ce/ci/variables/README.html

[S-Coyle]

Struggled with this for a while, specifically trying to get GitLab CI to check all of the commits in the MR, not just latest.

The above suggestions didn’t quite work for me, but I seem to have a winning script which my CI triggers

#!/bin/bash

# Need to fetch origin so we can calculate the shas of the branches
git fetch origin

# Get the target & source branch shas using their names, which is provided by the CI job
export TARGET_BRANCH_SHA=$(git rev-parse origin/$CI_MERGE_REQUEST_TARGET_BRANCH_NAME)
export SOURCE_BRANCH_SHA=$(git rev-parse origin/$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME)
echo "TARGET_BRANCH_SHA = " $TARGET_BRANCH_SHA
echo "SOURCE_BRANCH_SHA = " $SOURCE_BRANCH_SHA

# Now run commitlint using the standard conventional commit config
echo "Checking MR commit messages..."
npx commitlint -x @commitlint/config-conventional --from=${TARGET_BRANCH_SHA} --to=${SOURCE_BRANCH_SHA} --verbose

Hopefully it helps someone else who comes across this

[oupala]

I finally followed this piece of chunk.

Here is my working snippet to make commit linting work with GitLab CI/CD:

  script:
   - npm install
   - npx commitlint --from=master to=CI_BUILD_REF_NAME

Assuming you’re always merging to master (I can’t find the destination branch while merging).