Thanks for helping improve Bridgelet! Please read this guide before opening an issue or pull request.
- Follow the Code of Conduct in all community spaces.
- Start with the Support Guide to choose the right channel for questions vs. bugs.
- For security issues, do not open a public issue; follow
SECURITY.md.
- Report bugs: Use GitHub Issues with clear reproduction steps, expected vs. actual behavior, logs, and environment details.
- Ask questions or propose ideas: Use GitHub Discussions for how-to topics, design feedback, and feature requests.
- Improve docs: Submit PRs for docs corrections or clarifications.
- Code contributions: Focus on well-scoped changes with tests when applicable.
- Keep PRs focused; prefer small, reviewable changes.
- Include tests or notes on why tests are not required.
- Update documentation when behavior or APIs change.
- Link related issues/discussions and describe the approach and rationale.
- See the repository README and
/docsfor architecture and setup details. - Align with existing patterns and follow project style where present.
If you are unsure how to proceed, open a GitHub Discussion or email the maintainers per SUPPORT.md. We are happy to help you get started.
- Governance — outlines project roles, decision-making, and contributor participation.