mirror of
https://github.com/snapotter-hq/SnapOtter.git
synced 2026-08-03 07:46:42 +02:00
- Remove all lite/full variant logic from frontend, API, shared constants, docs, and tests (single unified Docker image only) - Replace single QEMU multi-arch Docker build with per-architecture native builds (amd64 + arm64) and manifest merge to fix disk space exhaustion - Add disk cleanup step and per-platform build cache scopes - Switch release trigger from push to workflow_dispatch - Add GitHub issue templates and PR template
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
# Contributing to Stirling Image
|
|
|
|
Thanks for your interest in the project. Community feedback helps shape Stirling Image, and there are several ways to get involved.
|
|
|
|
## How to contribute
|
|
|
|
The best way to contribute is through [GitHub Issues](https://github.com/stirling-image/stirling-image/issues):
|
|
|
|
- **Bug reports** - Found something broken? Open a bug report with steps to reproduce, your Docker setup, and what you expected to happen.
|
|
- **Feature requests** - Have an idea for a new tool or improvement? Describe the problem you want solved and why it matters to you.
|
|
- **Feedback** - Thoughts on the UI, workflow, documentation, or anything else? We want to hear it.
|
|
|
|
## Pull requests
|
|
|
|
We do not accept pull requests. All development is handled internally to maintain architectural consistency and code quality across the project.
|
|
|
|
If you've found a bug, please open an issue describing it rather than submitting a fix. If you have a suggestion for how something should work, describe it in a feature request. Your input is valuable even without a code contribution.
|
|
|
|
## Forking
|
|
|
|
You're welcome to fork the project for your own use under the terms of the [AGPLv3 license](LICENSE). The [Developer Guide](https://stirling-image.github.io/stirling-image/guide/developer) covers setup, architecture, and how to add new tools.
|
|
|
|
## Security
|
|
|
|
If you discover a security vulnerability, please report it privately through [GitHub Security Advisories](https://github.com/stirling-image/stirling-image/security/advisories/new) rather than opening a public issue.
|