|
1 | | -### Contributing Guidelines |
2 | | - |
3 | | -Thank you for considering contributing to QuantResearchStarter! |
4 | | - |
5 | | -#### Getting Started |
6 | | -- Fork the repo and create your branch from `main`. |
7 | | -- Python 3.10+ is required. |
8 | | -- Install in editable mode: `pip install -e .[dev]`. |
9 | | -- Run tests and linters locally: `make test` and `make lint`. |
10 | | - |
11 | | -#### Development Workflow |
12 | | -- Create a focused branch: `feature/<short-name>` or `fix/<short-name>`. |
13 | | -- Write unit tests for new features and bug fixes. |
14 | | -- Ensure `ruff` and `black` pass. |
15 | | -- Update documentation and docstrings as needed. |
16 | | - |
17 | | -#### Pull Requests |
18 | | -- Fill in the PR template. |
19 | | -- Keep PRs small and focused. |
20 | | -- Include before/after behavior when applicable. |
21 | | -- Link related issues. |
22 | | - |
23 | | -#### Good First Issues |
24 | | -- Look for issues labeled `good-first-issue` or `help-wanted`. |
25 | | -- Comment on an issue to get assigned. |
26 | | - |
27 | | -#### Code Style |
28 | | -- Follow PEP8 with `ruff` and `black` formatting. |
29 | | -- Use type hints for public functions. |
30 | | -- Keep functions small and readable. |
31 | | - |
32 | | -#### Testing |
33 | | -- Tests live under `tests/` and run with `pytest`. |
34 | | -- Aim for ~70% coverage of core modules. |
35 | | - |
36 | | -#### Commit Messages |
37 | | -- Use imperative tone: "Add X", "Fix Y". |
38 | | -- Reference issues: `Fixes #123`. |
39 | | - |
40 | | -#### Security |
41 | | -- See `SECURITY.md` to report vulnerabilities. |
42 | | - |
43 | | -We appreciate your contributions! |
44 | | - |
45 | | - |
46 | | - |
| 1 | +### Contributing Guidelines |
| 2 | + |
| 3 | +Thank you for considering contributing to QuantResearchStarter! |
| 4 | + |
| 5 | +#### Getting Started |
| 6 | +- Fork the repo and create your branch from `main`. |
| 7 | +- Python 3.10+ is required. |
| 8 | +- Install in editable mode: `pip install -e .[dev]`. |
| 9 | +- Run tests and linters locally: `make test` and `make lint`. |
| 10 | + |
| 11 | +#### Development Workflow |
| 12 | +- Create a focused branch: `feature/<short-name>` or `fix/<short-name>`. |
| 13 | +- Write unit tests for new features and bug fixes. |
| 14 | +- Ensure `ruff` and `black` pass. |
| 15 | +- Update documentation and docstrings as needed. |
| 16 | + |
| 17 | +#### Pull Requests |
| 18 | +- Fill in the PR template. |
| 19 | +- Keep PRs small and focused. |
| 20 | +- Include before/after behavior when applicable. |
| 21 | +- Link related issues. |
| 22 | + |
| 23 | +#### Good First Issues |
| 24 | +- Look for issues labeled `good-first-issue` or `help-wanted`. |
| 25 | +- Comment on an issue to get assigned. |
| 26 | + |
| 27 | +#### Code Style |
| 28 | +- Follow PEP8 with `ruff` and `black` formatting. |
| 29 | +- Use type hints for public functions. |
| 30 | +- Keep functions small and readable. |
| 31 | + |
| 32 | +#### Testing |
| 33 | +- Tests live under `tests/` and run with `pytest`. |
| 34 | +- Aim for ~70% coverage of core modules. |
| 35 | + |
| 36 | +#### Commit Messages |
| 37 | +- Use imperative tone: "Add X", "Fix Y". |
| 38 | +- Reference issues: `Fixes #123`. |
| 39 | + |
| 40 | +#### Security |
| 41 | +- See `SECURITY.md` to report vulnerabilities. |
| 42 | + |
| 43 | +We appreciate your contributions! |
| 44 | + |
| 45 | + |
| 46 | + |
0 commit comments