Thanks for contributing to Flux Kontext Template.
- Keep each pull request focused on one problem.
- Prefer fixes that reduce complexity instead of adding more configuration.
- Do not commit secrets, production data, or copied
.envfiles. - Update docs when behavior, setup, or public APIs change.
- Install dependencies with
npm ci. - Copy
env.exampleto.env.local. - Fill in the required environment variables for Supabase, auth, and Fal.
- Start the app with
npm run dev.
Run the checks that match your change:
npm run buildnpm run lintnpm run checknpm run test:api
If a change cannot be fully validated locally, call that out in the PR.
- Explain the problem, not just the code diff.
- Include screenshots for UI changes.
- Mention any new environment variables.
- Call out migrations, destructive actions, or rollout concerns.
Conventional commits are preferred:
fix: ...feat: ...chore: ...docs: ...
Do not open public issues for vulnerabilities. Follow the process in
SECURITY.md.