Server : Apache/2.4.41 (Ubuntu) System : Linux absol.cf 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory :  /usr/share/doc/node-yargs/

Upload File : current_dir [ Writeable ] document_root [ Writeable ]

# 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.