SDLC Enforce is LaneSync’s own GitHub status check. It is always required on protected branches alongside checks from your sdlc.yaml.
What it does
The bootstrappedsdlc-enforce GitHub Action:
- Runs on pull requests targeting protected branches
- Evaluates SDLC policy (milestone linkage, branch rules, stage constraints)
- Posts a commit status named
SDLC Enforce - Fails the check when policy is violated — blocking merge via rulesets
Relationship to other checks
SDLC Enforce is an infrastructure constant. It is not configured in sdlc.yaml and must not be removed from rulesets.Bootstrapped workflow
LaneSync pushes CI templates during repo bootstrap. The enforce step is part of.github/workflows/ci-*.yml:
{{CI_CHECK_NAME}}, {{DEV_BRANCH}}, etc.) are replaced during bootstrap.
Failure scenarios
Check pending indefinitely
Check pending indefinitely
Workflow did not run — verify branch protection targets correct branches and workflow
on: triggers include PR events.Check fails on valid PR
Check fails on valid PR
Review action logs. Common causes: missing milestone link on issues, PR targets wrong branch, repo bootstrap incomplete.
Check missing from rulesets
Check missing from rulesets
Re-run bootstrap or push
sdlc.yaml to trigger ruleset refresh. Full-tier app required for auto-rulesets.Development stage vs enforce action
These layers serve different purposes:
A PR can pass
SDLC Enforce while the milestone remains in DEVELOPMENT due to open issues or failed CI checks listed in sdlc.yaml.
Self-hosted
Self-hosted LaneSync instances use the same check name. SetSDLC_API_URL in repository variables so the action reaches your API. See Enterprise security.