glib/.gitlab-ci/run-check-todos.sh

#!/bin/bash

set -e

source .gitlab-ci/search-common-ancestor.sh

./.gitlab-ci/check-todos.py "${newest_common_ancestor_sha}"
ci: Add checks for banned keywords in merge requests Using the same approach as we have for code style checks (the `style-check-diff` CI job), check the diff for any banned keywords like ‘TODO’, and also check the commit messages. The keyword ‘TODO’ is often used by developers to indicate a part of a commit which needs further work, and hence which shouldn’t yet be merged. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1551 2019-04-25 11:23:26 +01:00			`#!/bin/bash`

ci: Ensure run-check-todos.sh exits on the first error it encounters Signed-off-by: Philip Withnall <withnall@endlessm.com> 2020-02-25 11:46:59 +00:00			`set -e`
ci: Add checks for banned keywords in merge requests Using the same approach as we have for code style checks (the `style-check-diff` CI job), check the diff for any banned keywords like ‘TODO’, and also check the commit messages. The keyword ‘TODO’ is often used by developers to indicate a part of a commit which needs further work, and hence which shouldn’t yet be merged. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1551 2019-04-25 11:23:26 +01:00
Move common code for searching common ancestor in a dedicated script Signed-off-by: Frederic Martinsons <frederic.martinsons@sigfox.com> 2021-01-11 17:03:34 +01:00			`source .gitlab-ci/search-common-ancestor.sh`
ci: Limit depth of fetch for initial code checks Rather than fetching the entire repository history, limit the fetch depth to commits in the last 4 weeks. If a branch was branched longer than 4 weeks ago, it seems reasonable to require it to be rebased before it can be reviewed. At the current rate of development, this reduces the bandwidth needed for git pulls in the initial code checks from 73MB to 9MB. Signed-off-by: Philip Withnall <withnall@endlessm.com> 2020-07-25 00:36:33 +01:00
ci: Add checks for banned keywords in merge requests Using the same approach as we have for code style checks (the `style-check-diff` CI job), check the diff for any banned keywords like ‘TODO’, and also check the commit messages. The keyword ‘TODO’ is often used by developers to indicate a part of a commit which needs further work, and hence which shouldn’t yet be merged. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1551 2019-04-25 11:23:26 +01:00			`./.gitlab-ci/check-todos.py "${newest_common_ancestor_sha}"`