From 7d63d87a8621aa853266b3bf01a128f810b618fc Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Tue, 9 Jun 2026 09:59:13 +0200 Subject: [PATCH 1/3] Add org policy to prevent accidental repo transfer GitHub has a feature to limit repository transfers which we could take advantage of --- transfer-repo-into-the-org.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/transfer-repo-into-the-org.md b/transfer-repo-into-the-org.md index 3ce11a3..b752123 100644 --- a/transfer-repo-into-the-org.md +++ b/transfer-repo-into-the-org.md @@ -47,10 +47,11 @@ is approved. ## Step 3. Transfer the repository -When the request is approved, the owner of the repository can start transferring -the repository into the Node.js GitHub organization. The person can be made a -member of the Node.js GitHub organization so they have the necessary permissions -to complete the transfer. +When the request is approved, the owner of the repository can be added to the allow list of the +[Organisation Repository Policy](https://github.com/organizations/nodejs/settings/policies/repositories) +so they can start transferring the repository into the Node.js GitHub organization. The person can +be made a member of the Node.js GitHub organization so they have the necessary permissions +to complete the transfer. After the transfer is complete, the allow list should be emptied. See [GitHub's documentation on transferring repos][] on how to perform the necessary actions. From 48e2c9a47e178e278f169caee1f66c0cad566299 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Tue, 9 Jun 2026 10:25:21 +0200 Subject: [PATCH 2/3] Bypass list should not be amended, actually --- transfer-repo-into-the-org.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/transfer-repo-into-the-org.md b/transfer-repo-into-the-org.md index b752123..dcf39f6 100644 --- a/transfer-repo-into-the-org.md +++ b/transfer-repo-into-the-org.md @@ -47,11 +47,11 @@ is approved. ## Step 3. Transfer the repository -When the request is approved, the owner of the repository can be added to the allow list of the -[Organisation Repository Policy](https://github.com/organizations/nodejs/settings/policies/repositories) -so they can start transferring the repository into the Node.js GitHub organization. The person can -be made a member of the Node.js GitHub organization so they have the necessary permissions -to complete the transfer. After the transfer is complete, the allow list should be emptied. +When the request is approved, the owner of the repository can start transferring +the repository into the Node.js GitHub organization. The person can be made a +member of the Node.js GitHub organization so they have the necessary permissions +to complete the transfer. A TSC member will need to approve the bypass request for the +[Organisation Repository Policy](https://github.com/organizations/nodejs/settings/policies/repositories). See [GitHub's documentation on transferring repos][] on how to perform the necessary actions. From 92c826dc217242f168cafa4f99e0e35bc030f285 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Tue, 9 Jun 2026 10:29:11 +0200 Subject: [PATCH 3/3] add link to bypass requests --- transfer-repo-into-the-org.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/transfer-repo-into-the-org.md b/transfer-repo-into-the-org.md index dcf39f6..273f215 100644 --- a/transfer-repo-into-the-org.md +++ b/transfer-repo-into-the-org.md @@ -50,7 +50,8 @@ is approved. When the request is approved, the owner of the repository can start transferring the repository into the Node.js GitHub organization. The person can be made a member of the Node.js GitHub organization so they have the necessary permissions -to complete the transfer. A TSC member will need to approve the bypass request for the +to complete the transfer. A TSC member will need to approve the +[bypass request](https://github.com/organizations/nodejs/settings/rules/bypass_requests) for the [Organisation Repository Policy](https://github.com/organizations/nodejs/settings/policies/repositories). See [GitHub's documentation on transferring repos][] on how to perform the