We maintain high standards to ensure the software we build together is production-ready. Here is how we ship.
Every PR must include updated documentation. If you add a feature, explain how it works.
Use descriptive commit messages. Squash small fix-ups to keep the repository history readable.
Every contribution requires at least one mentor approval. Be patient and responsive to feedback.
Fork the repository and create a feature branch.
Run local tests and ensure no regression.
Open a Draft PR to signal your work-in-progress.
Request review once the logic is finalized.
Address mentor feedback and merge.