Privacy Levels: migrate protected projects to private #7608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All protected projects should be private for .org and .com. Next step is to send an email to all .org users that have private projects.
stsewd
force-pushed
the
migrate-protected-projects
branch
from
c895769
to
a579991
Compare
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I have a draft in trello of an email we can send to users about this change |
humitos
approved these changes
Jan 21, 2021
Yes, we want to remove the protected level from projects, and remove all privacy levels from .org, the hidden attribute is for versions (we already migrated them). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
All protected projects should be private for .org and .com.
Next step is to email all .org users that have private
projects.