We use Github issues to track public bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
This is a rough outline of what a contributor's workflow looks like:
-
Search GitHub for an open or closed PR that relates to your submission. You don't want to duplicate effort.
-
Fork the repo and create your branch
topic
from master. -
Make your changes in a new git branch.
-
Make sure your code lints by running
npm run lint
command if present. -
Run the build with
npm run build
and test withnpm run test
command if present, and ensure that all build and test are succeeded. -
Commit your changes using a descriptive commit message that follows our commit message conventions.
-
Push your branch to GitHub forked repo.
-
In GitHub, submit a pull request to dagonmetric/lib-tools.
-
If you haven’t signed the CLA, you will see a automatic comment in the pull request. Click on the Details link. You will see the CLA. Click on sign in with Github to agree. And authorize CLA assistant to use your Github account to sign the CLA.
That's it! Thank you for your contribution. After your pull request is merged, you can safely delete your branch 'topic'.
By contributing to, you agree that your contributions will be licensed under the LICENSE file in the root directory of this source tree.