Skip to content

Latest commit

 

History

History
20 lines (11 loc) · 1.75 KB

CONTRIBUTING.md

File metadata and controls

20 lines (11 loc) · 1.75 KB

How to contribute to Underscore.js

  • This project adheres to a code of conduct. By participating, you are expected to uphold this code.

  • Please do not open a ticket to report a security issue. Consult the security policy on what to do instead.

  • Before you open a ticket or send a pull request, search for previous discussions about the same feature or issue. Add to the earlier ticket if you find one.

  • If you're proposing a new feature, make sure it isn't already implemented in Underscore-Contrib.

  • When contributing code, make sure that you edit the source code in the modules/ directory. Also, run npm install before committing any changes to ensure that our commit hooks can do their work.

  • Before sending a pull request for a feature, be sure to have tests.

  • Use the same coding style as the rest of the codebase.

  • In your pull request, do not add documentation or re-build the minified underscore-umd-min.js file. We'll do those things before cutting a new release.

"Help, cloning fails with fatal: fsck error in packed object"

This error is caused by zero-padded file modes in the commit history. As fixing this is highly destructive, we suggest ignoring these warnings. The simplest way is to instruct git to do so when cloning. For example, to clone from jashkenas/underscore, run the following command: git clone --config transfer.fsckobjects=false [email protected]:jashkenas/underscore.git. If cloning from a different user or organization, replace jashkenas with their name in the previous command.