chore: update contributing guide and enable CI on develop branch

* Updates the contributing guide with local setup instructions using uv, and adds steps for running lint, formatting, type checks, tests, and docs preview before opening a PR.

*Extends the CI workflow to also trigger on pushes and pull requests targeting the develop branch.

Author: Attakay78

.github/workflows/ci.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [main]
+    branches: [main, develop]
   pull_request:
-    branches: [main]
+    branches: [main, develop]
 
 jobs:
   test:

docs/contributing.md

@@ -20,19 +20,71 @@ For smaller changes like typo fixes, documentation improvements, or obvious bug
 
 ### Local setup
 
+The project uses [uv](https://docs.astral.sh/uv/) for dependency management.
+
 ```bash
 git clone https://github.com/Attakay78/fastapi-taskflow
 cd fastapi-taskflow
-pip install -e ".[dev]"
+uv sync
+```
+
+PRs should target the `develop` branch, not `main`.
+
+### Checks to run before opening a PR
+
+Run all of the following and make sure they pass cleanly.
+
+**Lint**
+
+```bash
+uv run ruff check .
+```
+
+**Format**
+
+```bash
+uv run ruff format --check .
+```
+
+To auto-fix formatting:
+
+```bash
+uv run ruff format .
 ```
 
-### Running tests
+**Type checking**
+
+```bash
+uv run mypy fastapi_taskflow
+```
+
+**Tests**
+
+```bash
+uv run pytest
+```
+
+All tests must pass. If you are adding a feature, include tests that cover the new behaviour.
+
+### Docs and README
+
+If your change affects user-facing behaviour, update the relevant page under `docs/` or `README.md` before opening the PR.
+
+To preview the docs site locally:
+
+```bash
+uv run mkdocs serve
+```
+
+Then open [http://127.0.0.1:8000/fastapi-taskflow](http://127.0.0.1:8000/fastapi-taskflow) in your browser. The server reloads automatically as you edit files under `docs/` or `mkdocs.yml`.
+
+To do a one-off build without serving:
 
 ```bash
-pytest
+uv run mkdocs build
 ```
 
-All tests must pass before a PR will be reviewed. If you are adding a feature, include tests that cover the new behaviour.
+The output goes to `site/`. That directory is gitignored and does not need to be committed.
 
 ### Code style