Skip to content

For Import linter, suggest __init__.py files when INP rules are not s…#821

Merged
nathanjmcdougall merged 2 commits intomainfrom
817-for-import-linter-suggest-__init__py-files-when-inp-rules-are-not-enabled
Jun 28, 2025
Merged

For Import linter, suggest __init__.py files when INP rules are not s…#821
nathanjmcdougall merged 2 commits intomainfrom
817-for-import-linter-suggest-__init__py-files-when-inp-rules-are-not-enabled

Conversation

@nathanjmcdougall
Copy link
Copy Markdown
Collaborator

…elected

@codspeed-hq
Copy link
Copy Markdown

codspeed-hq bot commented Jun 28, 2025

CodSpeed Instrumentation Performance Report

Merging #821 will not alter performance

Comparing 817-for-import-linter-suggest-__init__py-files-when-inp-rules-are-not-enabled (5814615) with main (5c4f993)

Summary

✅ 2 untouched benchmarks

@nathanjmcdougall nathanjmcdougall merged commit e059276 into main Jun 28, 2025
19 checks passed
@nathanjmcdougall nathanjmcdougall deleted the 817-for-import-linter-suggest-__init__py-files-when-inp-rules-are-not-enabled branch June 28, 2025 04:03
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.

For Import linter, suggest __init__.py files when INP rules are not enabled

1 participant