Skip to content

Print message to use __init__.py when using Import Linter without ruff#753

Merged
nathanjmcdougall merged 2 commits into
mainfrom
684-explain-that-__init__-is-needed-when-using-import-linter
Jun 16, 2025
Merged

Print message to use __init__.py when using Import Linter without ruff#753
nathanjmcdougall merged 2 commits into
mainfrom
684-explain-that-__init__-is-needed-when-using-import-linter

Conversation

@nathanjmcdougall

Copy link
Copy Markdown
Collaborator

No description provided.

@nathanjmcdougall nathanjmcdougall linked an issue Jun 15, 2025 that may be closed by this pull request
@codspeed-hq

codspeed-hq Bot commented Jun 15, 2025

Copy link
Copy Markdown

CodSpeed Walltime Performance Report

Merging #753 will not alter performance

Comparing 684-explain-that-init-is-needed-when-using-import-linter (84002ba) with main (889f64a)

Summary

✅ 1 untouched benchmarks

@codecov

codecov Bot commented Jun 15, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@nathanjmcdougall nathanjmcdougall merged commit 59a585c into main Jun 16, 2025
19 checks passed
@nathanjmcdougall nathanjmcdougall deleted the 684-explain-that-__init__-is-needed-when-using-import-linter branch June 16, 2025 23:27
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.

Explain that __init__ is needed when using Import Linter

1 participant