Contributing
How to contribute to Dexaflow — workflow, standards, and the TDD gate.
Version v0.5.5 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Contribute
Contribute to Dexaflow — the workflow, the local dev loops, and how to build these docs.
How to work on Dexaflow 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
dexaflow lite hot-reload loop for DAGs, and make lite-redeploy for Go changes.
Set up your loop →
Recipes
Step by step for the common changes: a migration, a setting, an API endpoint, a Helm value, a CLI flag, a connector, a backport, a release candidate.
Follow a recipe →
Review checklists
What to verify when reviewing Airflow compatibility, Kubernetes behavior, docs and developer experience, and where the evidence comes from.
Review a change →
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 →Recipes
Step by step for the changes contributors make most often, each pointing to the script or make target that does the work.
Review checklists
What to check when you review a change in an area where knowing the domain is not enough, and where the evidence comes from.
The local dev loop
Two inner loops for working on Dexaflow from source — the dexaflow lite hot-reload loop for DAGs, and make lite-redeploy for Go changes.
Build the docs
Build and preview the Dexaflow 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.