Overview

We welcome contributions of any size and contributors of any skill level. As an open-source project, we believe in giving back to our contributors. We are happy to help with guidance on PRs, technical writing, and turning any feature idea into a reality.

On this site, you will find several guides and resources for contributing to Astro’s documentation.

Project Repositories

Visit Colibri’s GitHub profile to find the repositories for:

• The client, website, and native client, as well as related shared libraries.
• The AppView, our backend service.

Setting up

Before writing code, get the stack running locally: Development walks through the AppView, the client and the website, and Running a PDS covers the one dependency that needs real setup.

Types of Contributions

In addition to contributing your own code or content, you can also make a huge contribution by getting involved by leaving review comments on PRs, adding ideas in existing GitHub Issues and Discussions, and participating in our “Pinned” issue maintenance tasks!

Every PR, especially translation PRs, needs reviewers! Reviewing PRs and leaving comments, suggestions, or an approving “LGTM!” (“Looks Good To Me!”) is a great way to get started in any repository, and to learn more about Astro.

If you have questions, feel free to join the Colibri Social Community on Colibri or tag the @colibri.social account on Bluesky.

Making a PR

When making a pull request, be sure to add a changeset when something has changed in an app / package. Changes to the website, docs, or repo configs do not need changesets.

pnpm changeset:feature

Add tests alongside your change where there is something to assert. Pure helpers and XRPC wrappers are cheap to cover and are where regressions actually bite. Testing explains what belongs where. If you touched a lexicon, run pnpm lexicons:export and commit the generated JSON, or CI will reject the PR.

---

Based on Astro’s Contributor Guide