-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f491bf1
commit f126b1b
Showing
1 changed file
with
61 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Contributing to Tranzlate | ||
|
||
Thank you for your interest in contributing to Tranzlate! Whether you want to report a bug, propose a new feature, or contribute code, we appreciate your help in making this tool better. | ||
|
||
## How Can I Contribute? | ||
|
||
### Reporting Bugs | ||
|
||
If you encounter a bug while using Tranzlate, please check if it hasn't been reported already by searching through our [issues](https://github.com/wkaisertexas/tranzlate/issues). If it's a new issue, you can create a detailed bug report including: | ||
|
||
- Description of the issue | ||
- Steps to reproduce | ||
- Expected behavior | ||
- Actual behavior | ||
- Environment details (Node.js version, operating system, etc.) | ||
|
||
### Requesting Features | ||
|
||
You can request new features or improvements by creating a [feature request](https://github.com/wkaisertexas/tranzlate/issues/new?assignees=&labels=feature-request&template=feature_request.md&title=) issue. Provide a clear description of the feature and why it would be valuable. | ||
|
||
### Contributing Code | ||
|
||
We welcome contributions in the form of pull requests (PRs). To contribute code: | ||
|
||
1. Fork the repository and create your branch from `main`. | ||
2. Implement your changes, following the [coding style](#coding-style) and ensuring tests pass. | ||
3. Open a pull request with a clear description of your changes and the problem they solve. | ||
|
||
#### Coding Style | ||
|
||
- Follow existing code style and formatting conventions. | ||
- Document new code or changes using JSDoc comments where applicable. | ||
- Write clear commit messages explaining the purpose of each commit. | ||
|
||
## Setting Up Development Environment | ||
|
||
To set up the Tranzlate development environment: | ||
|
||
1. Clone the repository: | ||
|
||
```bash | ||
git clone https://github.com/wkaisertexas/tranzlate | ||
``` | ||
|
||
2. Install dependencies: | ||
|
||
```bash | ||
npm install | ||
``` | ||
|
||
3. Set up your OpenAI API key as described in the [Setup](#setup) section of the documentation. | ||
|
||
4. You're ready to start coding! Make your changes and test them locally. | ||
## Code Review Process | ||
All code contributions will go through a code review process. Be prepared to address feedback and iterate on your changes before they can be merged. | ||
## License | ||
By contributing to Tranzlate, you agree that your contributions will be licensed under the [MIT License](LICENSE). |