-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unnecessary prefixes from various .import-restrictions files #73932
Remove unnecessary prefixes from various .import-restrictions files #73932
Conversation
/assign @liggitt @neolit123 |
only tightens allowed prefixes /lgtm |
Found using script: https://gist.github.com/dims/384dea60754042f61d79233603034038 Just run using: `find . -name .import-restrictions | xargs python ~/junk/sanitize-import-boss.py` The removed entries are either packages that got moved/renamed/deleted but are still not cleaned up from .import-restrictions files. Change-Id: I92c400f74e6f012cc75539311ed4de280e25e918
3c8f27f
to
1d430a4
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
whoops. had to add a couple back (mac vs linux issue) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Found using script:
https://gist.github.com/dims/384dea60754042f61d79233603034038
Just run using:
find . -name .import-restrictions | xargs python sanitize-import-boss.py
The removed entries are either packages that got moved/renamed/deleted
but are still not cleaned up from .import-restrictions files.
Change-Id: I92c400f74e6f012cc75539311ed4de280e25e918
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: