| Server IP : 14.225.204.176 / Your IP : 216.73.216.6 Web Server : nginx/1.24.0 System : Linux nodejs-ybgk 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 x86_64 User : root ( 0) PHP Version : 8.1.34 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /proc/thread-self/root/usr/share/doc/node-yargs/ |
Upload File : |
# 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.