style: apply Ruff formatting fixes

[Smartappli]

Motivation

• Fix the failing ruff-format pre-commit hook by applying repository formatting to satisfy ruff rules.

Description

• Run ruff format across the codebase and reformat 14 Python files under tracker/ to normalize line breaks, trailing commas, parentheses, and general whitespace; no functional logic changes were made.
• Files touched include admin, compatibility, forms, management commands, models, numerous tests, urls, and views within tracker/.
• Formatting changes are limited to layout (wrapping long expressions, consistent indentation, trailing commas, and grouping of literals) and do not change program behavior.

Testing

• Ran ruff format to apply formatting changes and it completed successfully.
• Verified formatting with ruff format --check, which reported all files already formatted (pass).

---

Codex Task

Summary by CodeRabbit

• Style

  • Improved code formatting across multiple files for better readability and consistency.

• Chores

  • Applied formatting standards to configuration files and test code.

---

Note: This release contains internal code organization improvements with no visible changes to user-facing functionality.

[coderabbitai]

Warning

Rate limit exceeded

@Smartappli has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 28 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 28 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a727d5c5-aa88-4419-a94e-c4a0388c1fa7

📥 Commits

Reviewing files that changed from the base of the PR and between 32743cb and be81a13.

📒 Files selected for processing (5)

• .github/workflows/ci.yml
• .github/workflows/codeql.yml
• .github/workflows/release-drafter.yml
• README.md
• pyproject.toml

📝 Walkthrough

Walkthrough

This is a comprehensive code formatting and style update across configuration and source files, reformatting long expressions into multi-line structures for improved readability while preserving all functional logic and behavior.

Changes

Cohort / File(s)	Summary
Configuration Files .github/release-drafter.yml	YAML formatting adjustment for the autolabeler entry, correcting trailing whitespace in the title: line.
Django Models & Admin tracker/admin.py, tracker/models.py	Reformatted ObservationSegmentAdmin.list_display tuple and IndependentVariableDefinition.set_values field declaration to multi-line format; removed extra blank lines.
Django Forms tracker/forms.py	Expanded FileField definitions, Meta.labels dictionaries, field lists, and help-text string construction across multiple lines; no functional changes to form behavior.
Management Commands tracker/management/commands/export_project_bundle.py, tracker/management/commands/release_report.py	Updated help string attributes from double-quoted to single-quoted format (content unchanged).
Core Logic tracker/compatibility.py	Reformatted normalize_session_payload, normalize_project_payload, compare_project_payloads, and build_roundtrip_report across multiple lines; value-selection logic and return types preserved.
Views & URLs tracker/views.py, tracker/urls.py	Reformatted segment_batch_assign member-id construction and multiple Django path() declarations to multi-line format; no routing or control flow changes.
Test Files tracker/tests/test_compatibility.py, tracker/tests/test_helpers.py, tracker/tests/test_i18n.py, tracker/tests/test_models.py, tracker/tests/test_roundtrip.py, tracker/tests/test_views.py	Expanded test setup calls, assertions, payload/fixture literals, and client requests across multiple lines; removed extraneous blank lines; no test logic or assertion behavior modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Possibly related PRs

• Release 0.9.2: batch segment assignment, refined review-queue filters, and CSV analytics export #5: Both PRs modify segment_batch_assign in tracker/views.py; the retrieved PR extends segment assignment and review-queue features while this PR reformats the member-id construction logic.

Poem

🐰 Lines so long, now neatly spread,
Multi-line declarations, clean and fed,
Whitespace dancing, trailing comma grace,
Code reads sweeter in a formatted space,
No logic changed, just beauty's chase! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'style: apply Ruff formatting fixes' accurately summarizes the main change: applying Ruff code formatter fixes across the repository.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-ruff-format-errors

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.