Skip to content

Latest commit

 

History

History
77 lines (54 loc) · 4.8 KB

CONTRIBUTING.md

File metadata and controls

77 lines (54 loc) · 4.8 KB

Contributing to Viron


We would like to encourage everyone to help and support this project by contributing.

We manage tasks using the GitHub Project where you can see which issue is in progress, is done, or has high priority.

How Can I Contribute?

Reporting Bugs

Please submit a GitHub issue to report a bug. Before submitting one, try to make sure any issue similar to your's doesn't already exist.

Suggesting Enhancements

Please submit a GitHub issue to suggest a enhancement.

Code Contribution

We apply the monorepo architecture; see each workspace's README.md for details.

Use the npm command's option --workspace with a workspace name to execute workspace-specific npm scripts, like:

$ npm run develop --workspace=@viron/app
$ npm run build --workspace=@viron/app --workspace=@viron/lib

Use the --workspaces option to execute a npm script on each workspace.

$ npm run test --workspaces

Below is a quick guide to code contribution.

  1. Fork and clone the repo to your local machine.
  2. Create a new branch from develop with a meaningful name for the task you work on.
  3. Setup by running: npm install . --legacy-peer-deps. (Important: npm version >= 7.9.0)
  4. Do your work following the styleguide of each package; read the readme.md files in each package directory.
  5. Add changelog intentions by running npm run changelog:intent.
  6. Push your branch.
  7. Submit a pull request to the upstream repository.

Code of Conduct

Follow this.

License

By contributing to this project, you agree to license your contribution under the MIT license.

Contributors

Thank you all who have contributed to this project.


fkei

🤔 💻

cathcheeno

🤔 💻 🌍 📖 📝

noritama

🤔 💻

babarl

🎨

MuuKojima

💻

tosaka07

💻

Jung0

💻

TakahisaKodama

💻

syama666

💻

takoring

💻

nezuu

💻

ishikawa-pro

💻

niwattitti

💻

ejithon

🤔