We are always looking for ways to make our modules better. Adding features and fixing bugs allows everyone who depends on this code to create better, more stable applications. Feel free to raise a pull request to us. Our team would review your proposed modifications and, if appropriate, merge your changes into our code. Ideas and other comments are also welcome.
- Create your own fork of this repository.
# Clone it
$ git clone git@github.com:me/beaver-logger.git
# Change directory
$ cd beaver-logger
# Add the upstream repo
$ git remote add upstream git://github.com/krakenjs/beaver-logger.git
# Get the latest upstream changes
$ git pull upstream
# Install dependencies
$ npm install
# Run scripts to verify installation
$ npm test
$ npm run-script lint
$ npm run-script cover- Make sure that your changes adhere to the current coding conventions used throughout the project, indentation, accurate comments, etc.
- Lint your code regularly and ensure it passes prior to submitting a PR:
$ npm run lint. - Ensure existing tests pass (
$ npm test) and include test cases which fail without your change and succeed with it.
- Don't check in your
./distfolder. You can use this command to ignore it without modifying the .gitignore file:git update-index —assume-unchanged dist/*.* - Ensure that no errors are generated by ESLint.
- Commit your changes in logical chunks, i.e. keep your changes small per single commit.
- Locally merge (or rebase) the upstream branch into your topic branch:
$ git pull upstream && git merge. - Push your topic branch up to your fork:
$ git push origin <topic-branch-name>. - Open a Pull Request with a clear title and description.
If you have any questions about contributing, please feel free to contact us by posting your questions on GitHub.
Copyright 2016, PayPal under the Apache 2.0 license.