Contributions and issue reports are encouraged and appreciated!
Before opening an issue, please check whether your issue has already been reported. Assuming it has not:
- Describe the issue you're encountering or the suggestion you're making
- Include any relevant steps to reproduce or code samples you can. It's always easier for us to debug if we have something that demonstrates the error.
- Let us know what version of this project you were using. If you're using a github checkout, provide the git hash.
Most pull requests should target the develop branch. master is the release branch. develop is periodically merged into master after a period of testing.
The summary line of your commit message should summarize the changes being made. Commit messages should be written in the imperative mood and should describe what happens when the commit is applied. If your commit modifies one of the in-tree haskell packages (found in ./lib), please prefix your commit summary with the name of the package being modified.
One way to think about it is that your commit message should be able to complete the sentence: "When applied, this commit will..."
Commits that update a dependency should include some information about why the dependency was updated in the commit message.
For breaking changes, new features, refactors, or other major changes, the body of the commit message should describe the motivation behind the change in greater detail and may include references to the issue tracker. The body shouldn't repeat code/comments from the diff.
Wherever possible, pull requests should add a single feature or fix a single bug. Pull requests should not bundle several unrelated changes.
Your pull request should add no new warnings to the project. It should also generally not disable any warnings.
Make sure the project builds and that the tests pass! This will generally also be checked by CI before merge, but trying it yourself first means you'll catch problems earlier and your contribution can be merged that much sooner!
You can run the tests like this:
$(nix-build -A selftest --no-out-link)To test that your changes build across platforms, you can also try to build release.nix, like this:
nix-build release.nixNote, however, that to build release.nix you must accept the android license agreement and your machine must be configured to build both ios and android executables (usually via remote builders).
We're always striving to improve documentation. Please include haddock documentation for any added code, and update the documentation for any code you modify.
In the Changelog
Add an entry to the changelog when your PR:
- Adds a feature
- Deprecates something
- Includes a breaking change
- Makes any other change that will impact users
In the Readme
The readme is the first place a lot of people look for information about the repository. Update any parts of the readme that are affected by your PR.
There are two ways to get live compiler feedback while developing Obelisk libraries. For libraries that are dependencies of the skeleton application, the easiest way to get feedback is to
cd skeleton
ob runThis ob run session only loads modules that are dependencies of the skeleton and obelisk-run. For example, obelisk-asset and obelisk-route are used by the skeleton.
For other libraries like obelisk-command you can use ghcid. To launch ghcid for lib/command you can run
nix-shell -A obeliskEnvs.obelisk-command --run "cd lib/command && ghcid"To re-install ob from source globally you can do
nix-env -f /path/to/obelisk -iA commandYou can also open a shell with the local version of ob available on your $PATH:
nix run -f /path/to/obelisk commandob will defer to the version found in your project's .obelisk/impl directory. To work on that version specifically:
ob thunk unpack ./.obelisk/impl
cd ./.obelisk/impl
# apply your changesIf you want to commit your changes, first push them to your fork of obelisk and then
cd /your/project/root
ob thunk pack .obelisk/impl
git add .obelisk/impl
git commit -m "Bump obelisk"