β¨ Contributing Guidelines
We welcome all contributions, including pull requests, bug reports, and discussions. Thank you for helping improve JANUX Authentication Gateway!
π Code of Conduct
Please review our Code of Conduct. All contributors are expected to follow it. Any inappropriate behavior or violations will not be tolerated.
β How to Get Help
See our Support Guide. Do not use GitHub issues for general questionsβask on Stack Overflow instead.
π Bug Reports & Issues
π DO
β Check the documentation & Support Guide before opening an issue.
β Search existing issues to avoid duplicates.
β Provide clear detailsβsteps to reproduce, error logs, expected vs. actual behavior.
β
Use Markdown formatting (wrap code in triple backticks ```
).
β DON'T
β Open duplicate issues.
β Comment "+1"βuse GitHub reactions instead.
π‘ Feature Requests
- Clearly describe the problem your feature solves.
- Explain why it's useful for others.
- If possible, outline a potential implementation.
- Avoid feature creepβwe prioritize core functionality.
π Submitting Pull Requests
Before submitting a PR:
β Open an issue first (for large changes).
β Keep PRs smallβone bug fix or feature per PR.
β Follow existing coding styles.
β Include tests and update documentation if necessary.
β Ensure CI checks pass before requesting review.
π PR Workflow
Step | Action Required |
---|---|
π Open Issue | Discuss the problem/feature first. |
ποΈ Fork & Code | Follow project structure, add tests. |
π Create PR | Provide a clear description. |
π Code Review | Address comments & improve PR. |
β Merge & Release | After approval, maintainers merge it. |
π Writing Commit Messages
Follow these commit message rules:
β Use the imperative mood β ("Fix crash", not "Fixed crash").
β Keep subject under 50 chars, and wrap body at 72 chars.
β Explain why the change is needed, not just what it does.
β Prefix relevant component β (e.g., [docs]
, [auth]
, [router]
).
Example:
[auth] Fix JWT token expiration issue
Updated the expiration logic to ensure tokens expire after 15 minutes.
Fixed bug where revoked tokens could still be used.
Resolves: #123
π Certificate of Origin
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
- The contribution was created in whole or in part by me and I have the right to submit it under the open-source license indicated in the file; or
- The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open-source license, and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open-source license (unless I am permitted to submit under a different license), as indicated in the file; or
- The contribution was provided directly to me by some other person who certified (1), (2), or (3), and I have not modified it.
- I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistently with this project or the open-source license(s) involved.
π Summary
π― Report bugs & feature requests properly.
π Follow PR & coding guidelines.
β Write clear commit messages.
π Respect the Code of Conduct.
π Thank you for contributing to JANUX Authentication Gateway!