Hey, thanks for being interested! Here's how we do things around here.
- Fork the repo (or clone directly if you're a member)
- Create a branch off
main - Do the thing
- Open a PR
We use prefixed branch names:
feature/short-description-- new stufffix/short-description-- bug fixeschore/short-description-- maintenance, deps, CI, docsexperiment/short-description-- things that may or may not work out
- Write a clear description of what changed and why
- Keep PRs focused -- one thing per PR when possible
- We're trust-based, so reviews aren't required, but a second pair of eyes never hurts
Code style varies by project. Check each repo's README for project-specific linting, formatting, and language conventions.
Found a bug? Have an idea? Open an issue. We have templates to help, but a blank issue is fine too.
By contributing, you agree that your contributions will be licensed under the same license as the project you're contributing to.