git / moonbite-core / test/lint/lint-git-commit-check.sh · raw

#!/usr/bin/env bash# Copyright (c) 2020 The Bitcoin Core developers# Distributed under the MIT software license, see the accompanying# file COPYING or http://www.opensource.org/licenses/mit-license.php.## Linter to check that commit messages have a new line before the body# or no body at allexport LC_ALL=CEXIT_CODE=0while getopts "?" opt; do  case $opt in    ?)      echo "Usage: $0 [N]"      echo "       COMMIT_RANGE='<commit range>' $0"      echo "       $0 -?"      echo "Checks unmerged commits, the previous N commits, or a commit range."      echo "COMMIT_RANGE='47ba2c3...ee50c9e' $0"      exit ${EXIT_CODE}    ;;  esacdone# TRAVIS_BRANCH will be present in a Travis environment. For builds triggered# by a pull request this is the name of the branch targeted by the pull request.# https://docs.travis-ci.com/user/environment-variables/if [ -n "${TRAVIS_BRANCH}" ]; then  COMMIT_RANGE="$TRAVIS_BRANCH..HEAD"fiif [ -z "${COMMIT_RANGE}" ]; then    if [ -n "$1" ]; then      COMMIT_RANGE="HEAD~$1...HEAD"    else      # This assumes that the target branch of the pull request will be master.      MERGE_BASE=$(git merge-base HEAD master)      COMMIT_RANGE="$MERGE_BASE..HEAD"    fifiwhile IFS= read -r commit_hash  || [[ -n "$commit_hash" ]]; do    n_line=0    while IFS= read -r line || [[ -n "$line" ]]; do        n_line=$((n_line+1))        length=${#line}        if [ $n_line -eq 2 ] && [ $length -ne 0 ]; then            echo "The subject line of commit hash ${commit_hash} is followed by a non-empty line. Subject lines should always be followed by a blank line."            EXIT_CODE=1        fi    done < <(git log --format=%B -n 1 "$commit_hash")done < <(git log "${COMMIT_RANGE}" --format=%H)exit ${EXIT_CODE}