Gecko [ thecigaretteboxes.com ]

Name	Size	Permission
examples	[ DIR ]	drwxr-xr-x
CHANGELOG-historical.md.gz	22.6 KB	-rw-r--r--
CODE_OF_CONDUCT.md	3.14 KB	-rw-r--r--
README.md	3.97 KB	-rw-r--r--
advanced.md.gz	5.39 KB	-rw-r--r--
api.md.gz	13.49 KB	-rw-r--r--
changelog.Debian.gz	910 B	-rw-r--r--
contributing.md	1.04 KB	-rw-r--r--
copyright	1.49 KB	-rw-r--r--
examples.md.gz	2.03 KB	-rw-r--r--
tricks.md	2.21 KB	-rw-r--r--
typescript.md	1.41 KB	-rw-r--r--
webpack.md	1.4 KB	-rw-r--r--

Code Editor : contributing.md

# Contributing to Yargs

Me hearties, we would love to have you contribute to yargs!

If you are looking to update the website, check out [yargs/yargs.github.io](https://github.com/yargs/yargs.github.io).

## Contributing

1. Look through the existing issues and see if your idea is something new.
2. Create a new issue, or comment on an existing issue that you would like
   to help solve:
    * it's usually best to get some feedback before proceeding to write code.
3. fork the yargs repo, and clone it to your computer:
    * GitHub has [great documentation](https://help.github.com/articles/using-pull-requests/) regarding writing your first pull request.
4. make sure that you write unit-test for any code that you write for yargs:
    * we use the [standard](https://github.com/feross/standard) coding style,
      which will validate your style when you run tests.
    * look through our extensive test suite in `/test` to get an idea for how
      to write unit-tests for this codebase.
5. make sure you are comfortable with the Code of Conduct outlined below.

${this.title}

Code Editor : contributing.md