Contributing¶
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report Bugs¶
Report bugs at https://github.com/climateimpactlab/isku/issues
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Fix Bugs¶
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement a fix for it.
Implement Features¶
Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
Write Documentation¶
isku could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such.
PRs with small corrections to spelling, format or clarity are welcome. The project has designed its documentation to make this process easier for non-technical users to contribute to documentation.
Submit Feedback¶
The best way to send feedback is to file an issue at https://github.com/climateimpactlab/isku/issues.
If you are proposing a new feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome.
Get Started!¶
Ready to contribute? Here's how to set up isku for local development.
Please note this documentation assumes you already have uv, just, and git installed and ready to go.
-
Fork the
iskurepo on GitHub. -
Clone your fork locally:
- Now we need to install the environment. Navigate into the directory
Then, install and activate the environment with:
- Install prek to run linters/formatters at commit time:
- Create a branch for local development:
Now you can make your changes locally.
-
Don't forget to add test cases for your added functionality to the
testsdirectory. -
When you're done making changes, check that your changes pass the lint tests.
Now, validate that automated tests are passing:
- Commit your changes and push your branch to GitHub:
git add .
git commit -m "Your detailed description of your changes."
git push origin name-of-your-bugfix-or-feature
- Submit a pull request through the GitHub website.
Documentation¶
Documentation is in the docs/ directory with global configurations in the .zensical file. Documentation is rendered with Zensical and hosted through GitHub Pages to https://climateimpactlab.github.io/isku/.
You can build and check any changes or additions you've made to documentation locally on your machine after you've set up your development environment.
Make a clean, validated build of the documentation with
You can build and serve the documentation pages locally with
and then view your changes in a web browser by following the on-screen URL.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
-
The pull request should include tests.
-
If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in
README.md.