Writing and maintaining documentation. Anything from typos to entire tutorials helps. Documentation contributions are done in the form of pull requests (see below). If you are using scide, there is a useful trick to setting up your workspace for documentation edits.

Pull requests

The first step to filing a PR is to get your git environment working. First, fork supercollider/supercollider on GitHub. By convention, origin should point to your fork, and upstream to the main repository:

Your changes are at the topic/my-great-improvement branch on your fork of SuperCollider. Now point your browser to your SuperCollider fork and file a PR. (The topic/ prefix is a Git convention used to mark a topic branch, which is a branch created for short-term development use. It helps organize the list of branches in your fork, but it’s also fine to leave it out.)

Here are some important guidelines for making pull requests:

Don’t put unrelated changes in the same pull request. Separate by functionality or issue.

Try not to change whitespace or needlessly rearrange things if they don’t have anything to do with the issue you are fixing. Save rearrangement for a separate commit.

Be patient! It might take a few days for your changes to get reviewed and merged. Smaller PRs get merged faster, which is another good reason to break down your contributions into bite-sized pieces.