Skip to content

Repo - we need to run the Julia Formatter on the entire repo and ensure consistency going forward #515

Open

Description

@jhalpern30

As the title says - run the Julia formatter on the repo, and make sure all developers and their LLMs use it going forward. It is distracting seeing a massive diff in a PR that is just formatting churn - do this after all major PRs are closed just before v2.0 comes out

Activity

  1. added this to the GPEC v2.0.0 milestone on Oct 8, 2026
  2. logan-nc commented on Oct 27, 2026

    @logan-nc
    Collaborator

    Measured tonight on develop db90e82 with JuliaFormatter v1.0.62 (the version .pre-commit-config.yaml pins): the sweep touches 88 files, +1212/−1064 lines, plus trailing whitespace in seven text files. Not opening it now, on purpose: it overlaps #569, #574, #581, #551 and #593 by 17–39 files each, so it would either conflict with all of them or force each to rebase through it. The sweep is mechanical and takes minutes to regenerate, so there is no value in an early PR. Plan: run it as the first PR after those five merge, then merge #356 (the CI gate) the same day so nothing drifts again.

  3. added theissue type on Oct 30, 2026
  4. logan-nc commented on Oct 30, 2026

    @logan-nc
    Collaborator

    @matt-pharr I just assigned you because your #356 will automatically satisfy this.
    If you want to close now to declutter, fine - otherwise, hopefully it is clear that no one should stress about this moving forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions