You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create private repo for inadvertent disclosures #573
I approve the creation of premature-disclosures but I don't think it should be a copy of nodejs/node. Let's make it an empty repo with a README that explains what it is about.
@targos that is what had created. Myles had pushed the node content when we thought there was still a possibility of moving a PR. Given that we can't removing all of that is what I had in mind as part of the "cleanup"
Is the assumption that CommComm and Moderation can have access to this repository, even though they wouldn't receive a disclosure through the proper channels? Since both teams are admins on the org they have access to any private repos.
Activity
gireeshpunathil commentedon Nov 24, 2020
I approve
mcollina commentedon Nov 24, 2020
I approve
targos commentedon Nov 24, 2020
I approve the creation of
premature-disclosuresbut I don't think it should be a copy ofnodejs/node. Let's make it an empty repo with a README that explains what it is about.mhdawson commentedon Nov 24, 2020
@targos that is what had created. Myles had pushed the node content when we thought there was still a possibility of moving a PR. Given that we can't removing all of that is what I had in mind as part of the "cleanup"
mhdawson commentedon Nov 30, 2020
Repo repurposed and cleanup. Maybe not in the best way but should do.
mmarchini commentedon Dec 7, 2020
Is the assumption that CommComm and Moderation can have access to this repository, even though they wouldn't receive a disclosure through the proper channels? Since both teams are admins on the org they have access to any private repos.