-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add CONTRIBUTING.md #47
base: main
Are you sure you want to change the base?
Conversation
Awesome! Thanks for taking care of this. I haven't read the content yet. Just a minor suggestion: let's add a link to the guide to README.md to increase its visibility |
@novusnota can you check this PR? :) |
### Reporting Issues | ||
|
||
- Include code snippets and error messages | ||
- Include as much detail as possible | ||
- Include steps to reproduce the issue | ||
- Include the version of tree-sitter you're using | ||
- Use code blocks for error messages and logs | ||
|
||
### Making Changes | ||
|
||
1. Fork the repository | ||
2. Create a new branch for your changes | ||
3. Make your changes | ||
4. Write or update tests as needed | ||
5. Ensure all tests pass | ||
6. Format the code using `npm run fmt` | ||
7. Submit a pull request | ||
|
||
### Pull Request Process | ||
|
||
1. Update the README.md if needed | ||
2. Follow the existing code style | ||
3. Include a clear description of your changes | ||
4. Link any related issues using keywords (e.g., "Fixes #123") | ||
5. Wait for review from maintainers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably removed this altogether or moved it somewhere to highlight the dev setup and the overall structure of the project which follows below
Fixes #35