Guardrails / git

No work in progress commits

git/no-wip-commits@v1

The build range carries no commit that says it was never meant to be merged.

Id	git/no-wip-commits
Version	v1
Category	git
Default severity	warning
Interpreter	python3
Timeout	30 seconds
Violations tolerated	0
Collects	git

Collectors

This guardrail gathers nothing itself. It depends on the collectors below, which the CLI runs once per build before any check, and reads what they found out of GUARDRAIL_FACTS. A collector that collects nothing skips this guardrail rather than failing it.

Collector	Gathers	Inputs it is given
git	The repository, HEAD, the remotes, and every commit between the base ref and HEAD with its message, author, parents and the files the range changed.	baseRef

The inputs above are this guardrail's own, passed straight through. Configuring one in buildnote.json changes what is collected, and two guardrails configured the same way share the one collection.

Configuration

{
  "guardrails": {
      "failOn": "error",
      "comment": true,
      "checks": [
          {
              "use": "git/no-wip-commits@v1",
              "severity": "warning",
              "with": {
                  "baseRef": "origin/main",
                  "markers": "fixup!,squash!,amend!,WIP,wip:,TEMP,DO NOT MERGE"
              },
              "exemptions": []
          }
      ]
  }
}

Inputs

Input	Description	Default	Environment variable
baseRef	Ref the range starts at. The commits checked are <baseRef>..HEAD.	origin/main	GUARDRAIL_INPUT_BASEREF
markers	Comma separated markers that make a commit subject a work in progress one.	fixup!,squash!,amend!,WIP,wip:,TEMP,DO NOT MERGE	GUARDRAIL_INPUT_MARKERS

How to fix

Rewrite the range before merging:

git rebase --interactive --autosquash origin/main

--autosquash folds fixup! and squash! commits into the ones they name. A WIP commit on a protected branch is a change nobody described, which is the same evidence problem as a commit with no work item.

More in git

• git/author-identity-domain. Every commit in the build range was authored and committed by an address on a domain the organisation controls.
• git/changed-files-budget. The build range changes few enough files that a reviewer can hold the whole change in their head.
• git/conventional-commits. Every commit message in the build range follows the Conventional Commits specification: the subject line, the blank line before the body, and the BREAKING CHANGE footer.
• git/no-merge-commits. The build range contains no merge commits.
• git/work-item-reference. Every commit in the build range, or the branch it is on, names the change record it belongs to.

All 6 git guardrails