jashkenas--coffeescript/CONTRIBUTING.md

## How to contribute to CoffeeScript

* Before you open a ticket or send a pull request, [search](https://github.com/jashkenas/coffeescript/issues) for previous discussions about the same feature or issue. Add to the earlier ticket if you find one.

* Before sending a pull request for a feature, be sure to have [tests](https://github.com/jashkenas/coffeescript/tree/master/test).

* Use the same coding style as the rest of the [codebase](https://github.com/jashkenas/coffeescript/tree/master/src). If you're just getting started with CoffeeScript, there's a nice [style guide](https://github.com/polarmobile/coffeescript-style-guide).

* In your pull request, do not add documentation to `index.html` or re-build the minified `coffee-script.js` file. We'll do those things before cutting a new release.
Adding a CONTRIBUTING to CoffeeScript. 2012-09-17 17:16:41 +00:00			`## How to contribute to CoffeeScript`

now that github supports renames, coffeescript, not coffee-script 2014-05-08 19:07:42 +00:00			`* Before you open a ticket or send a pull request, [search](https://github.com/jashkenas/coffeescript/issues) for previous discussions about the same feature or issue. Add to the earlier ticket if you find one.`
Adding a CONTRIBUTING to CoffeeScript. 2012-09-17 17:16:41 +00:00
now that github supports renames, coffeescript, not coffee-script 2014-05-08 19:07:42 +00:00			`* Before sending a pull request for a feature, be sure to have [tests](https://github.com/jashkenas/coffeescript/tree/master/test).`
Adding a CONTRIBUTING to CoffeeScript. 2012-09-17 17:16:41 +00:00
now that github supports renames, coffeescript, not coffee-script 2014-05-08 19:07:42 +00:00			`* Use the same coding style as the rest of the [codebase](https://github.com/jashkenas/coffeescript/tree/master/src). If you're just getting started with CoffeeScript, there's a nice [style guide](https://github.com/polarmobile/coffeescript-style-guide).`
Adding a CONTRIBUTING to CoffeeScript. 2012-09-17 17:16:41 +00:00
Ensure that all source files end with a single `\n` This was done by first checking all files in the repository root by hand, and then by doing the following: $ npm i get-stdin@4 $ cat clean.coffee fs = require 'fs' stdin = require 'get-stdin' stdin (text) -> for file in text.trim().split('\n') contents = fs.readFileSync file .toString().replace /\s$/, '\n' fs.writeFileSync file, contents return $ ls !(node_modules)//.coffee \| coffee clean.coffee 2015-09-03 17:20:12 +00:00			* In your pull request, do not add documentation to `index.html` or re-build the minified `coffee-script.js` file. We'll do those things before cutting a new release.