Getting started with coding

If you are a coder and want to help with the site, you can fork our GitHub repository and submit a pull request with your changes.

Setting up your local development environment

For instructions on cloning the repo, installing dependencies, and running the app locally, see the CONTRIBUTORS.md file in the main repository.

Local development setup

To decide whether you need to keep your coding work separate from your real identity, read Protecting your privacy. If you do, follow Create an Anonymous GitHub Account and Contributing Code Anonymously.

Not sure where to start? Use both of these:

AC.org task board — Organization-wide board for Activist Checklist work. Look in the Ready column for issues maintainers have marked as ready to pick up.
Open issues on the main app repository — Full list if you want to search or filter directly.

If an issue description is too brief or unclear, ask for clarification in the issue thread before you start coding.

Open task board

View open issues

Pick an issue

Start from the Ready column on the AC.org task board, or browse open issues on the main repository. Choose something that matches your skills and availability.

If there is no assignee yet, leave a comment to say you are working on it so effort does not get duplicated.
Fork the repo

Create your own copy of the main Activist Checklist repository:

Fork the main repository
Create a branch and make changes

Create a short branch name that describes your fix or feature, then implement and test your changes.

Keep pull requests focused on one issue when possible. Smaller PRs are easier and faster to review.
Open a pull request

Open a PR from your branch to ActivistChecklist/ActivistChecklist.

In the PR description, explain what changed, why it changed, and link the issue it resolves.
Address review feedback

We may request edits before merging. Push follow-up commits to the same branch and we will continue review in the same PR thread.