ProjectGuide 12 / 12

Contributing

Work on Stackiln itself and verify framework changes.

01

Before starting

Search issues and pull requests first. Open an issue before a large preset, module, dependency, or architecture change. Report vulnerabilities privately through GitHub Security Advisories.

02

Repository checks

The complete gate requires Docker. It validates Stackiln, independent marketing and accounts fixtures, PostgreSQL migrations, production builds, browser journeys, managed-file state, and a live non-root container.

pnpm install --frozen-lockfile
pnpm typecheck
pnpm test
pnpm lint
pnpm verify
03

Contribution rules

  • Keep pull requests focused and explain compatibility, security, and migration impact.
  • Add tests for observable behavior and documentation for user-visible changes.
  • Plans remain read-only and writes go through staging.
  • Disabled modules leave no routes, source, dependencies, environment requirements, schema, or navigation behind.
  • Never overwrite a changed managed file without an explicit conflict report.
04

License

Contributions are distributed under the MIT License. Generated products include STACKILN-LICENSE.md so the required notice follows Stackiln-derived source. Product teams own their original code, content, branding, and configuration.