First and foremost, thank you for your interest in contributing to Crynux Node! We welcome any form of contribution, whether it's reporting bugs, suggesting new features, or submitting code.
This guide is intended to help you get started with your contributions.
To foster an open and welcoming environment, we require all contributors and community members to adhere to our Code of Conduct. Please take a moment to read and understand it before participating.
We use GitHub Issues to track bugs and feature requests. Before you start writing code, please check the existing issues to see if there's one related to your contribution.
If you find a bug, please submit a new Issue. In your report, please describe the problem as detailed as possible, including:
- Your operating system and version.
- Relevant software versions (e.g., Python, Node.js, etc.).
- Detailed steps to reproduce the bug.
- The expected behavior and what actually happened.
- Please attach the log files according to this doc.
If you have an idea for a new feature, please let us know by submitting an Issue. Please describe the feature you would like to see, its use case, and why you think it would be beneficial to the project.
- Fork the repository: Click the "Fork" button on the top right of this page to fork the project to your own GitHub account.
- Clone the repository: Clone your forked repository to your local machine:
git clone https://github.com/YOUR_USERNAME/crynux-node.git cd crynux-node - Set up development environment: Please refer to the README.md to prepare the local development environment, and start the Crynux Node locally.
- Commit your changes:
We recommend using the Conventional Commits specification for writing commit messages.
git add . git commit -m "feat: A brief description of your changes" git push origin main
- Create a Pull Request: After pushing your code, go back to your forked repository page on GitHub and click the "New pull request" or "Compare & pull request" button. Please ensure you are merging your feature branch into the
mainbranch of the original repository. - Describe your PR: In the PR description, please clearly explain the changes you've made and link any relevant issues (e.g.,
Closes #123).
If you have any questions, feel free to reach out to us through the Crynux Discord:
Thank you again for your contribution!