Start by reading tibbe's style guide. Current Feldspar follows most of the conventions except for the section on data types.
Use your judgement. Having a line that is 83 characters long might be a better choice compared to the alternative even if it violates the style guide.
-
No commits to master in your fork.
-
Follow whatever code style the file uses. One consistent but bad style is preferable over having eight different good styles in the same file.
-
No trailing whitespace.
-
Run
cabal testbefore committing. -
Use one commit per logical change.
-
Keep the pile of small style fixes and similar in one or several separate commits.
-
Make a sensible commit message.