​
Before Reporting

​
Check Existing Issues

  1. Search the GitHub Issues and GitHub Discussions
  2. Review closed issues
  3. Check the documentation

​
Gather Information

  • Nile Auth version
  • Environment details
  • Steps to reproduce
  • Error messages
  • Relevant logs

​
Creating an Issue

​
Issue Template

### Description
[Clear description of the issue]

### Environment
- Nile Auth Version:
- Node.js Version:
- Operating System:
- Browser (if applicable):

### Steps to Reproduce
1. [First Step]
2. [Second Step]
3. [and so on...]

### Expected Behavior
[What you expected to happen]

### Actual Behavior
[What actually happened]

### Additional Context
[Any other relevant information]

​
Issue Types

​
Bug Reports

  • Describe the bug clearly
  • Provide reproduction steps
  • Include error messages
  • Add relevant code snippets

​
Feature Requests

  • Explain the use case
  • Describe expected behavior
  • Provide examples
  • Consider alternatives

​
Documentation Issues

  • Identify unclear sections
  • Suggest improvements
  • Point out errors
  • Propose additions

​
Best Practices

​
Writing Good Issues

  1. Be specific and clear
  2. One issue per report
  3. Include relevant details
  4. Use proper formatting

​
Issue Labels

  • bug: Bug reports
  • enhancement: Feature requests
  • documentation: Doc updates
  • help wanted: Community assistance needed
  • auth: Mark Nile Auth specific issues (not issues with the database, for instance)

​
Contributing Solutions

​
Fixing Issues

  1. Comment on the issue
  2. Fork the repository
  3. Create a fix
  4. Submit a pull request

​
Pull Request Guidelines

### Related Issue
Fixes #[issue number]

### Changes Made
- [Change 1]
- [Change 2]
- [Change 3]

### Testing Done
- [Test 1]
- [Test 2]

### Screenshots (if applicable)
[Add screenshots]

​
Security Issues

​
Responsible Disclosure

  1. DO NOT create public issues
  2. Email security@thenile.dev
  3. Wait for response
  4. Follow disclosure timeline

​
Security Guidelines

  • Report vulnerabilities privately
  • Provide proof of concept
  • Allow time for fixes
  • Follow up responsibly

​
Getting Help

​
Issue Lifecycle

  1. Submission
  2. Triage
  3. Investigation
  4. Resolution
  5. Closure

​
Best Practices

  • Be respectful and professional
  • Follow up on your issues
  • Help others when possible
  • Keep discussions focused