Contributing to Idris-Dev
The Idris Community welcomes pull requests, bug reporting, and bug squashing! However, we cannot do it all ourselves, and want to make it as easy as possible to contribute changes to get things working. Here are a few guidelines that we would like contributors to follow so that we can have a chance of keeping on top of things.
- Make sure you are familiar with Git.
- Make sure you have a GitHub account.
- Make sure you are familiar with: Idris.
- Make sure you can install Idris:
Before you report an issue, or wish to add cool functionality please try and check to see if there are existing issues and pull requests. We do not want you wasting your time, duplicating somebody's work!
Try as closely as possible to describe the issue, ensuring that it has sections that match the following headings:
# Steps to Reproduce
# Expected Behavior
# Observed Behavior
In addition, please attach complete source files that exhibit the issue to quoting from them in the issue.
We would be delighted to receive feature requests only if they are feasible to implement and the author is willing to implement the suggested features themself. The current Idris developer team consists mostly of volunteers, and so it is unfortunately hard to accommodate implementing nice-to-have ideas that are not essential for core language development.
The Campsite Rule
We try to follow the campsite rule: leave the code base in better condition than you found it. Please clean up any messes that you find, and don't leave behind new messes for the next contributor.
Contributing to the default libraries.
Idris ships with a set of packages in
libs/ that is provided as a default library.
preludeis a collection of basic definitions, automatically imported by Idris programs.
baseis tried and tested code that may be useful, and has seen active use in multiple projects.
contribis code that is experimental in design and that we want to test before possible inclusion in
effectsis a library which supports effectful programming.
These packages should not be seen as the standard as when working with dependent types; we do not necessarily know how best to work with dependent types yet. These packages offer functionality that can be built on top of when constructing Idris programs.
Everything in prelude will be imported automatically, unless given the
The contents of base are available with no special options, but modules must be imported.
The other two packages that ship with Idris, contrib and effects, require the use of the
-p command-line argument to bring their contents into the include path.
New contributions should be added to the contrib package (never directly to base or prelude!). If they turn out to be widely applicable and useful, they may later be moved into base.
As Idris is still being developed we are open to suggestions and changes that make improvements to these default packages. Major changes to the library, or Idris itself, should be discussed first through the project's official channels of communication:
- The mailing List.
- On our IRC Channel
#idrison freenode, or
- As an RFC in the issue tracker
Developers then seeking to add content to Idris's prelude and default library, should do so through a PR where more discussions and refinements can be made.
We do not want you wasting your time nor duplicating somebody's work!
Idris developers and hackers try to adhere to something similar to the successful git branching model. The steps are described below.
For those new to the project:
- Fork our main development repository
idris-devon github e.g.
- Clone your fork to your local machine:
$ git clone email@example.com:<your github user name>/Idris-dev.git
idris-lang/Idris-devas a remote upstream
$ git remote add upstream firstname.lastname@example.org:idris-lang/Idris-dev.git
For those already contributing to the project:
- Ensure your existing clone is up-to-date with current
$ git fetch upstream $ git merge upstream/master
The remaining steps are the same for both new and existing contributors:
- Create, and checkout onto, a topic branch on which to base you work.
- This is typically the master branch.
- Please avoid working on the
$ git branch fix/master/my_contrib master $ git checkout fix/master/my_contrib
- Make commits of logical units.
- Check for unnecessary whitespace with
$ git diff --check
Make sure your commit messages are along the lines of:
Short (50 chars or less) summary of changes More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, preceded by a single space, with blank lines in between, but conventions vary here
Make sure you have added any necessary tests for your changes.
Run all the tests to ensure nothing else was accidentally broken.
$ make test
- Push your changes to a topic branch in your fork of the repository.
$ git push origin fix/master/my_contrib
- Go to GitHub and submit a pull request to
From there you will have to wait on one of the
idris-dev committers to respond to the request.
This response might be an accept or some changes/improvements/alternatives will be suggest.
We do not guarantee that all requests will be accepted.
Increasing chances of acceptance.
To help increase the chance of your pull request being accepted:
- Run the tests.
- Update the documentation, the surrounding code, examples elsewhere, guides, whatever is affected by your contribution
- Use appropriate code formatting for both Idris and Haskell.
- Idris Wiki;
- Zen Of Idris;
- Idris FAQs: Official; Unofficial;
- Idris Manual;
- Idris Tutorial;
- Idris News;
- other Idris docs.
- Using Pull Requests
- General GitHub Documentation.