Thanks for helping improve Dockette repositories.
-
Start with an issue
- Search existing issues and pull requests first.
- For larger changes, open an issue before coding.
-
Fork and branch
- Fork the target repository.
- Create a branch from
master(for examplefix/nginx-hstsordocs/readme-update).
-
Keep changes focused
- Solve one problem per pull request.
- Follow existing code style and project structure.
- Update documentation when behavior or configuration changes.
-
Verify locally
- Run relevant checks (tests, linters, image builds if available).
- Avoid environment-specific behavior.
-
Open a pull request
- Use clear commit messages and explain why the change is needed.
- Link related issues (for example
Closes #123). - Describe what changed and how you tested it.
- Tests and checks pass locally.
- Documentation and examples are updated when needed.
- No secrets, tokens, or private credentials are committed.
- Breaking changes are clearly documented.
Do not open public issues for security vulnerabilities.
Follow the repository SECURITY.md disclosure instructions.