How to contribute
From first issue to merged pull request.
Thanks for wanting to make Mnemo better. Here is the short version of how contributions flow.
Find something to work on
Browse the issue tracker. Good first contributions are usually small and self-contained: a reproducible bug, a rough edge in the UI, a missing piece of documentation. Comment on the issue before starting so nobody duplicates the work.
Propose the change
- Fork the repository and create a branch for your change.
- Keep the change focused; one concern per pull request reviews faster.
- Explain the "why" in the pull request description, not just the "what".
- Write commit messages in the house format; Commits and pull requests has the details.
What review looks for
- Does it solve a real problem, and is the problem stated?
- Does it match the surrounding code's style and conventions?
- Is the user-facing behavior still honest and predictable?
Reviews are conversations, not gates. Expect questions, and ask them right back.
Documentation counts
These docs are markdown files in the website repository, and fixing them is a contribution like any other. If a guide confused you, the guide is the bug.