Guardrails / docs

Repository publishes a code of conduct

docs/code-of-conduct@v1

The repository has a CODE_OF_CONDUCT.md, so the standard contributors are held to, and who enforces it, is written down.

Id	docs/code-of-conduct
Version	v1
Category	docs
Default severity	info
Interpreter	python3
Timeout	30 seconds
Violations tolerated	0
Collects	files

Collectors

This guardrail doesn't gather anything itself. It relies on the collectors below, which the CLI runs once per build before any check, and reads what they found from GUARDRAIL_FACTS. If a collector collects nothing, this guardrail is skipped, not failed.

Collector	Gathers	Inputs it is given
files	Presence, size and line counts of the well known files a repository is expected to carry, plus any extra path the guardrail asks for.	path

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

Configuration

{
  "guardrails": {
      "failOn": "error",
      "checks": [
          {
              "use": "docs/code-of-conduct@v1",
              "severity": "info",
              "with": {
                  "path": "CODE_OF_CONDUCT.md",
                  "minLines": "5"
              },
              "exemptions": []
          }
      ]
  }
}

Inputs

Input	Description	Default	Environment variable
path	Path to the code of conduct, relative to the directory the CLI runs in.	CODE_OF_CONDUCT.md	GUARDRAIL_INPUT_PATH
minLines	How many non-blank lines it needs before it counts as published.	5	GUARDRAIL_INPUT_MINLINES

How to fix

Add a CODE_OF_CONDUCT.md at the repository root, or under .github/. Adopting an existing code of conduct is normal and just as good as writing your own. The Contributor Covenant is the usual choice, and the only part you need to fill in yourself is the address reports go to.

An unwritten standard is enforced inconsistently and can't be appealed, which hurts the person reporting more than the person reported.

More in docs

• docs/agent-instructions. The repository has an instruction file for coding agents, long enough to say something and short enough to be read in full.
• docs/changelog. The repository has a changelog, so what changed between two releases is written down instead of pieced together from commits.
• docs/contributing. The repository has a CONTRIBUTING.md explaining how a change is proposed, built and reviewed.
• docs/license-present. The repository has a licence file, so what people may do with the code is written down, not assumed.
• docs/readme. The repository has a README that says more than just its title.
• docs/security-policy. The repository has a SECURITY.md saying where to report a security problem.

All 7 docs guardrails