Thanks helping with the development of Elm! This document describes the basic standards for opening pull requests and making the review process as smooth as possible.
You need to sign the contributor agreement and send it to [email protected] before opening your pull request.
- Haskell — conform to these guidelines
- JavaScript — use Google's JS style guide
-
The master branch is the home of the next release of the compiler so new features and improvements get merged there. Most pull requests should target this branch!
-
The stable branch is for tagging releases and critical bug fixes. This branch is handy for folks who want to build the most recent public release from source.
If you are working on a fairly large feature, we will probably want to merge it in as its own branch and do some testing before bringing it into the master branch. This way we can keep releases of the master branch independent of new features.
Note that the master branch of the compiler should always be in sync with the master branch of the website, and the stable branch of the compiler should always be in sync with the stable branch of the website. Make sure that your changes maintain this compatibility.