This is a guide on how to contribute to Chikamichi.
Contributions are welcome 🎉
The following Issue is accepted.
- Questions about features
- Report errors or problems
- Propose additions or improvements to feature
Please click here to issue.
Pull requests are always welcome.
The following types of Pull Requests are accepted. For basic Pull Requests (especially minor ones), you may send a Pull Request without creating an Issue.
- Bug Fixes
- Add functionality
- Performance Fixes
- Typo Fixes
"How about this kind of fix/improvement?" If you have a question, please raise an Issue and discuss it with me.
Please follow these steps to create a pull request.
- Fork the repository
- Create a branch
- Add or modify feature
- Run e2e and unit test
- Check the feature in your browser
- Commit Changes
- Push branch
- Create Pull Request
Also, when creating a pull request, please keep the following in mind
- One pull request per feature - If you want to do more than one thing, send multiple pull requests.
- Add tests! - If you add a feature, it would be great if you could write a test for it.
- Keep the same style - eslint will automatically be ran before committing
- Document any change in behavior - Make sure the
README.md
and any other relevant documentation are kept up-to-date. - Send coherent history - Make sure your commits message means something
First, clone the forked repository locally.
$ git clone git@github.com:foo/chikamichi.git
Install dependent modules with pnpm. If you do not have pnpm, please install it beforehand.
$ pnpm i
The dev command starts the development server.
$ pnpm run dev
When the development server starts, the Extension build results are output to the extension
.
You can use extensions in your browser by loading the contents of the extensions folder in Chrome Exteinsions.
When you modify the code, the change is automatically reflected.
Chikamichi have e2e test and unit test.
Run unit test.
$ pnpm run test
Run e2e test.
$ pnpm run cypress:open
That's it. Happy coding 👍