Skip to content

Conversation

@Ana06
Copy link
Member

@Ana06 Ana06 commented Aug 14, 2025

This PR reformats the entire codebase using the 'black' code formatter to ensure a consistent and readable style. The formatting was applied with the command: black --line-length=120 .

To maintain this style, a new GitHub Actions workflow (.github/workflows/ci.yml) has been added. This CI job automatically runs black --check on all pushes and pull requests.

Automating style enforcement is beneficial for project health because it:

  • Improves Code Review Efficiency: Reviewers can focus on the core logic and functionality of a change, rather than spending time on manual formatting nitpicks.
  • Ensures Consistency: A uniform style makes the codebase easier to read, understand, and maintain for everyone.
  • Lowers Contribution Barrier: Contributors don't have to guess the project's style rules; the linter provides immediate, automated feedback.

You can see the workflow running in the following example PR (it fails on purpose): Ana06#5. It should also run in this PR (and not fail as the offenses are fixed):

This commit reformats the entire codebase using the 'black' code
formatter to ensure a consistent and readable style. The formatting was
applied with the command: `black --line-length=120 .`

To maintain this style, a new GitHub Actions workflow
(`.github/workflows/ci.yml`) has been added. This CI job automatically
runs `black --check` on all pushes and pull requests.

Automating style enforcement is crucial for project health because it:
- **Improves Code Review Efficiency:** Reviewers can focus on the core
  logic and functionality of a change, rather than spending time on
manual formatting nitpicks.
- **Ensures Consistency:** A uniform style makes the codebase easier to
  read, understand, and maintain for everyone.
- **Lowers Contribution Barrier:** Contributors don't have to guess the
  project's style rules; the linter provides immediate, automated
feedback.
@Ana06 Ana06 self-assigned this Aug 14, 2025
@tinajohnson tinajohnson added this to the v3.6 milestone Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants