jmiller
94ff15c128
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 34s
Non-workflow docs/config only (CLAUDE.md, README, branch-protection, ISSUE_TEMPLATE/config.yml, ci-issue-reporter). Workflow files, manifest schema, and Makefile install paths left for the forge-rebrand gate. Authored-by: Moko Consulting
35 lines
1013 B
Markdown
35 lines
1013 B
Markdown
# Contributing to MokoSuiteBackup
|
|
|
|
Thank you for your interest in contributing to MokoSuiteBackup.
|
|
|
|
## Getting Started
|
|
|
|
1. Fork the repository on MokoGitea
|
|
2. Create a feature branch from `dev` (`feature/your-feature`)
|
|
3. Make your changes following the coding standards below
|
|
4. Submit a pull request targeting `dev`
|
|
|
|
## Branch Strategy
|
|
|
|
- `main` — stable releases only
|
|
- `dev` — active development
|
|
- `feature/*` — new features (target `dev`)
|
|
- `fix/*` — bug fixes (target `dev`)
|
|
- `hotfix/*` — urgent fixes (target `dev` or `main`)
|
|
|
|
## Coding Standards
|
|
|
|
- PHP 8.1+ required
|
|
- Follow Joomla coding standards
|
|
- SPDX license headers on all PHP files
|
|
- Use `SubscriberInterface` for event subscription
|
|
- Use `bind() -> check() -> store()` for Table operations
|
|
|
|
## Reporting Issues
|
|
|
|
Report bugs and feature requests via [Issues](https://git.mokoconsulting.tech/MokoConsulting/MokoSuiteBackup/issues).
|
|
|
|
## License
|
|
|
|
By contributing, you agree that your contributions will be licensed under GPL-3.0-or-later.
|