We take Pull Requests!
- Contact the contributors via the Discord channel or the Github Issue to make sure that this is issue or bug should be handled with proposed way. Send details of your case and explain the details of the proposed solution.
- Once you get approval from one of the maintainers, you can start to work on your code change.
- After your changes are ready, make sure that you covered your case with automated tests and verify that you have limited the number of breaking changes to a bare minimum.
- We also highly appreciate any relevant updates to the documentation.
- Make sure that your code is compiling and all automated tests are passing.
- Make sure that you applied or answered all the feedback from the maintainers.
- We're trying to be as much responsive as we can, but if we didn't respond to you, feel free to ping us on the Discord channel.
- Pull request will be merged when you get approvals from at least one of the maintainers (and no rejection from others). Pull request will be tagged with the target Emmett version in which it will be released. We also label the Pull Requests with information about the type of change.
We try to limit the number of necessary setup to a minimum, but few steps are still needed:
Available here.
If you're using NVM you can also call:
nvm install
and
nvm use
To use current recommended version.
Available here.
You are now ready to contribute to Emmett.
You can streamling setup by running setup script:
- For Linux and MacOS
./setup.sh
- For Windows
.\buildScript.ps1
Or perform manual steps
Source codes are located under ./src/ folder.
cd src
npm install
npm run build
npm run test
If any of those steps didn't work for you, please contact us on Discord channel.
Emmett is using NPM Workspaces.
The source codes are located in src folder. Packages are nested under ./src/packages folder.
For documentation Emmett is using Vitepress. Documentation is located under ./src/docs folder.
To build documentation locally, run in src
folder:
npm run docs:dev
See also other helpful scripts in ./src/package.json.
- Fork the repository.
- Create a feature branch from the
main
branch. - We're not squashing the changes and using rebase strategy for our branches (see more in Git documentation). Having that, we highly recommend using clear commit messages. Commits should also represent the unit of change.
- Before sending PR to make sure that you rebased the latest
main
branch from the main Emmett repository. - When you're ready to create the Pull Request on GitHub.
Emmett is using the recommended TypeScript, ESLint and Prettier coding style configurations. They should be supported by all popular IDE (eg. Visual Studio Code, WebStorm) so if you didn't disabled it manually they should be automatically applied after opening the solution. We also recommend turning automatic formatting on saving to have all the rules applied.
By contributing to Emmett:
- You assert that contribution is your original work.
- You assert that you have the right to assign the copyright for the work.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community.