e3b5181b19
- Updated comments in LeadsListScreen, MoreScreen, TaskDetailScreen, TaskFormScreen, TasksListScreen, TicketAnalyticsScreen, TicketDetailScreen, TicketsListScreen, ApiService, AuthService, CrashReporting, DealCard, TicketCard, MultiSelectSheet, KanbanColumn, StageStepper, TicketApprovalPanel, TicketPropertiesCard, and TicketTimePanel to improve readability and maintain a consistent style. - Adjusted punctuation and phrasing for better flow and understanding.
2.4 KiB
2.4 KiB
Contributing to BottleCRM
Thank you for helping improve BottleCRM. Contributions of all sizes are welcome, including bug fixes, features, tests, documentation, and accessibility improvements.
Before You Start
- Search the existing issues before opening a new one.
- For a substantial feature or architectural change, open an issue first so the approach can be discussed before implementation begins.
- Keep pull requests focused. Unrelated changes are easier to review when submitted separately.
Development Setup
Full instructions (cloning, Docker, the backend (uv), the frontend (pnpm), running the mobile app, adding dependencies, and running tests) live in the documentation site under Contributing:
- Development setup. Get all three projects running locally.
- Testing, running the suite, markers, and what CI runs.
- Code style, Python, frontend, and Flutter conventions, and what CI does and doesn't enforce.
- Repository layout, where each part of the codebase lives.
- Security rules. The rules this codebase treats as non-negotiable.
- Adding an org-scoped model. What a new multi-tenant model needs, including its RLS policy.
Submitting a Pull Request
- Create a branch from
masterwith a descriptive name. - Make focused changes and include tests where appropriate.
- Run the relevant development checks. See Testing and Code style.
- Update documentation when behavior, setup, or public APIs change.
- Push your branch and open a pull request against
master.
In the pull request description, explain what changed, why it changed, how it was tested, and include screenshots for visible UI changes. See Pull requests for what CI runs and what review focuses on.
Pull Request Checklist
- The change is focused and does not include unrelated edits.
- Relevant backend and frontend checks pass.
- Tests cover new or changed behavior where practical.
- Required migrations are included.
- Documentation is updated.
- No credentials, tokens, or private data are committed.