Contributing
How to contribute to Leoflow — workflow, standards, and the TDD gate.
Contribute
Contribute to Leoflow — the workflow, the local dev loops, and how to build these docs.
How to work on Leoflow itself.
Start here
Contributing
The workflow, the code-quality standards, and the TDD gate every change passes.
Read the guide →
The local dev loop
The
leoflow lite hot-reload loop for DAGs, and make lite-redeploy for Go changes.
Set up your loop →
Build the docs
Build and preview this Hugo + Docsy site locally.
Build the site →
Handling secrets
The two rules — private locality and masked-on-read — every feature that touches a credential must follow (ADR 0061).
Read the rules →
Image scanning
Where container CVE findings appear, what blocks a build and what only opens an issue, and how to triage either one.
Read the policy →The local dev loop
Two inner loops for working on Leoflow from source — the leoflow lite hot-reload loop for DAGs, and make lite-redeploy for Go changes.
Build the docs
Build and preview the Leoflow documentation site locally — Hugo + Docsy.
Handling secrets in a feature
The two rules every feature that touches a credential must follow — private locality and masked-on-read — with the patterns to satisfy them.
Container image vulnerability scanning
Where container CVE findings appear, what blocks a build and what only opens an issue, and how to triage either one.