Skip to content

Latest commit

 

History

History
33 lines (20 loc) · 1 KB

CONTRIBUTING.md

File metadata and controls

33 lines (20 loc) · 1 KB

Contributing

  1. Fork the project and clone your fork.

  2. Create a local feature branch:

    $ git checkout -b <branch>
    
  3. If adding a function R.foo, define it in src/foo.js and include unit tests in test/foo.js. If adding an internal function _foo, define it in _src/internal/foo.js.

  4. Make one or more atomic commits. Each commit should have a descriptive commit message, wrapped at 72 characters. Do not commit changes to dist/ramda.js.

  5. Run make test lint, (or grunt test) and address any errors. Preferably, fix commits in place using git rebase or git commit --amend to make the changes easier to review and to keep the history tidy.

  6. Push to your fork:

    $ git push origin <branch>
    
  7. Open a pull request.

Conventions

  • Do not use Array.prototype.push. Use xs[idx] = x or xs[xs.length] = x rather than xs.push(x). See #890 for links to related pull requests.