[ci] Move code for quick lint job into bash scripts
This shouldn't cause any changes to behaviour, but I have done a bit
of cleaning up (using the magic pathspec arguments to git diff to
simplify some things, and avoiding creating files in $PWD, to make
this nicer to run locally).
The idea is that a developer can now run
ci/jobs/quick-lint.sh
to get roughly the same tests as are run by the quick lint step for a
pull request in CI.
Signed-off-by: Rupert Swarbrick <rswarbrick@lowrisc.org>
diff --git a/ci/scripts/lint-commits.sh b/ci/scripts/lint-commits.sh
new file mode 100755
index 0000000..83bf01f
--- /dev/null
+++ b/ci/scripts/lint-commits.sh
@@ -0,0 +1,35 @@
+#!/bin/bash
+# Copyright lowRISC contributors.
+# Licensed under the Apache License, Version 2.0, see LICENSE for details.
+# SPDX-License-Identifier: Apache-2.0
+
+# A wrapper around lint_commits.py, used for CI.
+#
+# Expects a single argument, which is the pull request's target branch
+# (usually "master").
+
+if [ $# != 1 ]; then
+ echo >&2 "Usage: lint-commits.sh <tgt-branch>"
+ exit 1
+fi
+tgt_branch="$1"
+
+merge_base="$(git merge-base --fork-point origin/$tgt_branch)" || {
+ echo >&2 "Failed to find fork point for origin/$tgt_branch."
+ exit 1
+}
+echo "Checking commit messages since $merge_base"
+
+# Notes:
+# * Merge commits are not checked. We always use rebases instead of
+# merges to keep a linear history, which makes merge commits disappear
+# ultimately, making them only a CI artifact which should not be
+# checked.
+# * 'type=error' is used even for warnings. Only "errors" are shown in
+# the GitHub checks API. However, warnings don't return a non-zero
+# error code so don't fail the build step.
+util/lint_commits.py \
+ --no-merges \
+ --error-msg-prefix="##vso[task.logissue type=error]" \
+ --warning-msg-prefix="##vso[task.logissue type=error]" \
+ "$merge_base"..HEAD
