Thank you for your interest in contributing to Lictor! We appreciate your help and support. This document outlines the guidelines and best practices for contributing to this project.
Please read and follow our Code of Conduct to ensure a positive, inclusive, and welcoming environment for everyone.
There are many ways to contribute to this project:
- Report bugs or request features by opening an issue.
- Improve existing code, documentation, or tests.
- Add new features or enhancements.
Before submitting a bug report or feature request, please check the issue tracker to see if your issue has already been reported or is being worked on. If it doesn't already exist, create a new issue with a clear title and description, following the provided issue templates.
To contribute code, follow these steps:
- Fork the repository and create your branch from the
main
branch. - If you've added code, make sure to add appropriate tests.
- Ensure that the test suite passes by running
npm test
. - Follow the coding style enforced by the project, including ESLint and Prettier configurations.
- Commit your changes with a clear, concise, and descriptive commit message, following the conventional commit format.
- Push your branch to your fork on GitHub.
- Create a pull request against the
main
branch of the original repository.
Once you've submitted a pull request, the project maintainers will review your changes. They may ask for changes or improvements before merging your changes. Be patient and responsive to feedback, and be prepared to make updates to your pull request if necessary.
To set up your local development environment, follow these steps:
- Clone the repository to your local machine.
- Run
yarn install
to install the project's dependencies. - Run
yarn start
to start the development server. Open your browser and navigate tohttp://localhost:3000
to view the app. - Make your changes, and test them locally.
- Run
npm test
to ensure that all tests pass before submitting your changes.
This project uses ESLint and Prettier to enforce consistent coding style. Please ensure that your changes adhere to the
provided configurations. You can check your code by running npm run lint
, and you can automatically fix most issues by
running npm run lint:fix
.
By contributing to this project, you agree that your contributions will be licensed under the project's LICENSE file.