Skip to content

ci: add line length lint step using nightly cargo fmt#34997

Open
antiguru wants to merge 1 commit intoMaterializeInc:mainfrom
antiguru:cargo_fmt
Open

ci: add line length lint step using nightly cargo fmt#34997
antiguru wants to merge 1 commit intoMaterializeInc:mainfrom
antiguru:cargo_fmt

Conversation

@antiguru
Copy link
Member

Summary

  • Add a new CI lint step that runs cargo +nightly fmt -- --check --config error_on_line_overflow=true to catch overly long lines in Rust source files.

Test plan

  • Verify the new lint-line-length step appears in CI and runs successfully
  • Confirm it catches lines exceeding the configured max width

🤖 Generated with Claude Code

@antiguru antiguru requested a review from a team as a code owner February 12, 2026 21:43
@github-actions
Copy link

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

@antiguru antiguru force-pushed the cargo_fmt branch 2 times, most recently from 50857a0 to 06e2744 Compare February 12, 2026 21:58
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants