-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Remove usage of project.privacy_level #7013
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
Conversation
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.
Makes sense to me. We can merge it after today's deploy.
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.
This seems simple enough, it's mostly just finishing up the work we've been doing previously. Is there any change required on .com here? Are we removing it there too?
@ericholscher yes, it's #878 on corp. Fix for the flaky tests in on #7137 |
@stsewd need the redirect now 👍 |
Test should pass after #6535
If this is approved I can create a redirect to the new section.
Closes #4743
Partially closes / #2663