Skip to content

chore: execute goimports to format the code#757

Closed
promalert wants to merge 1 commit intocrytic:masterfrom
promalert:master
Closed

chore: execute goimports to format the code#757
promalert wants to merge 1 commit intocrytic:masterfrom
promalert:master

Conversation

@promalert
Copy link
Copy Markdown

@promalert promalert commented Jan 7, 2026

Description

execute goimports to format the code

Type of Change:

  • Bug Fix
  • New Feature
  • Refactoring
  • Documentation
  • Performance Improvement
  • Tests
  • Other (please describe):

Testing

Additional Context

Outstanding TODOs

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jan 7, 2026

CLA assistant check
All committers have signed the CLA.

Copy link
Copy Markdown
Member

@dguido dguido left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change is directionally correct - standardized imports are good practice. However, a few issues:

  1. Incomplete application: This only fixes 20 files, but there are more files with non-standard import ordering. Consider running goimports -w . on the entire codebase.

  2. CI enforcement missing: Without adding goimports to CI, the codebase will drift back to inconsistent formatting. Consider adding to the lint job:

    - name: Check imports
      run: |
        go install golang.org/x/tools/cmd/goimports@latest
        test -z "$(goimports -d .)"
  3. PR type: The type is marked as "Documentation" but this is a formatting/style change.

Suggested next steps:

  1. Run goimports -w . on the entire codebase
  2. Add goimports check to CI
  3. Update PR description

dguido added a commit that referenced this pull request Jan 20, 2026
- Run goimports -w . on entire codebase to standardize import ordering
- Add goimports check to CI lint job to prevent drift
- Addresses review feedback on PR #757

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@dguido
Copy link
Copy Markdown
Member

dguido commented Jan 20, 2026

This PR has been superseded by #764 which:

  1. Runs goimports -w . on the entire codebase (addressing the review feedback about incomplete coverage)
  2. Adds a goimports check to CI to prevent drift

Thank you @promalert for the original contribution! 🙏

dguido added a commit that referenced this pull request Jan 20, 2026
- Run goimports -w . on entire codebase to standardize import ordering
- Add goimports check to CI lint job to prevent drift
- Addresses review feedback on PR #757

Co-Authored-By: Claude Opus 4.5 <[email protected]>
dguido added a commit that referenced this pull request Jan 20, 2026
- Run goimports -w . on entire codebase to standardize import ordering
- Add goimports check to CI lint job to prevent drift
- Addresses review feedback on PR #757

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@dguido
Copy link
Copy Markdown
Member

dguido commented Jan 20, 2026

Closing in favor of #764 which addresses the review feedback.

@dguido dguido closed this Jan 20, 2026
dguido added a commit that referenced this pull request Jan 20, 2026
- Run goimports -w . on entire codebase to standardize import ordering
- Add goimports check to CI lint job to prevent drift
- Addresses review feedback on PR #757

Co-Authored-By: Claude Opus 4.5 <[email protected]>
dguido added a commit that referenced this pull request Jan 20, 2026
- Run goimports -w . on entire codebase to standardize import ordering
- Add goimports check to CI lint job to prevent drift
- Addresses review feedback on PR #757

Co-authored-by: Claude Opus 4.5 <[email protected]>
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.

3 participants