29 lines
966 B
Markdown
29 lines
966 B
Markdown
# Contributing
|
|
|
|
Want to contribute? Great! I'll be happy to review your contributions.
|
|
|
|
**Note:** Pull requests, merge requests, and issues opened on the platform itself are not accepted. All contributions are handled via email.
|
|
|
|
## Reporting issues
|
|
|
|
Send an email to `hi [at] andros.dev` with the subject `Issue: Issue title` and include:
|
|
|
|
- Repository name
|
|
- Detailed description of the issue
|
|
- Optional attachments (screenshots, logs, relevant information)
|
|
|
|
## Submitting patches
|
|
|
|
1. Clone the repository and create a feature branch
|
|
2. Make your changes and test thoroughly
|
|
3. Generate a patch with `git format-patch`
|
|
4. Send an email to `hi [at] andros.dev` with the subject `Patch: Patch title`, attach the `.patch` files, and include the repository name and a detailed description
|
|
|
|
## Best practices
|
|
|
|
- One patch addresses one logical change
|
|
- Test before submitting
|
|
- Write clear commit messages
|
|
- Be patient with maintainers
|
|
- Accept feedback constructively
|