Fortress is open source and open to contributions. Bug fixes, new features, performance work, docs, and tests are all welcome.
- For anything bigger than a small fix, open an issue first so we can agree on the approach before you write code.
- Fork the repo and branch from
main. - Keep the patch focused. One change per PR.
- Open a PR describing what changed and why. A maintainer will review it.
Changes to patches/, the SDK, packaging, and .github/workflows/ require maintainer review, see .github/CODEOWNERS. CI on PRs from forks runs after a maintainer approves the workflow run.
The one hard restriction: no PR may add or change branding. This means no third-party attribution, badges, brand strings, logos, or "built with" credits anywhere in the repo. Fortress is not affiliated with any outside party, and PRs implying otherwise will be closed without review. If your change is code, it's welcome; if it touches naming or attribution, it isn't.
Open an issue for bugs, questions, or feature requests. Reproduction steps help.