01
1. Provision the API key
- Open /settings/api-keys, click Create key. Name it after the repo (e.g. acme-chat-api).
- Copy the didk_ prefix exactly once — the raw value is never shown again.
- In the repo, Settings → Secrets → Actions → New repository secret. Name: DOESITDEFEND_API_KEY. Value: paste the didk_ key.
02
2. Add the workflow
- Create `.github/workflows/llm-gate.yml` and use the Action path shown in the CI Integration reference.
- Set `endpoint`, `api-key`, the API format (`template`), and the failure rule (`fail-on`). These fields define what is tested and how the result affects the check.
- Open a pull request and confirm that GitHub records the check. Runtime depends on the target and selected scenarios.
03
3. Choose when the check fails
- Use `fail-on: regression` to fail only when the result worsens against a comparable prior run. Without a valid prior run, the first result is informational.
- Use `fail-on: findings` when any open finding must fail the check, including on the first run.
- Use `fail-on: never` while adopting the workflow so the team can inspect results without blocking changes. Operational errors remain separate from security verdicts.