For some reason, importing a system from zip is turning some members private when they weren't before. Hopefully it isn't exposing previously private members to the public. CHECK!!!!
For some reason, importing a system from zip is turning some members private when they weren't before. Hopefully it isn't exposing previously private members to the public. CHECK!!!!
Ok, details: Every member who's latest blog post is set to private, gets their profile set to private on export. I changed a variable name from just "privacy" which gets re-used a lot, to "member_privacy" and it seems to have fixed it, but that variable name was already unique in that scope so I'm not convinced. Pushing anyway
Ok, details: Every member who's latest blog post is set to private, gets their profile set to private on export. I changed a variable name from just "privacy" which gets re-used a lot, to "member_privacy" and it _seems_ to have fixed it, but that variable name was already unique in that scope so I'm not convinced. Pushing anyway
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For some reason, importing a system from zip is turning some members private when they weren't before. Hopefully it isn't exposing previously private members to the public. CHECK!!!!
Ok, details: Every member who's latest blog post is set to private, gets their profile set to private on export. I changed a variable name from just "privacy" which gets re-used a lot, to "member_privacy" and it seems to have fixed it, but that variable name was already unique in that scope so I'm not convinced. Pushing anyway
this is lit fine now