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
Copy file name to clipboardExpand all lines: MIGRATION.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Logan currently has several scattered public repositories. The goal is to consol
9
9
|**LAF-PUBLIC**| All publicly shareable projects and work |
10
10
|**LAF-PRIVATE**| Private, sensitive, or work-in-progress content |
11
11
12
-
A **GitHub Organization**(e.g., `loganfinney27-lab` or `LAF-org`) is recommended to host both repos and enable cleaner access control, team collaboration, and branding. See [GitHub's guidance on Organizations](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations).
12
+
A **GitHub Organization**named **LAF-US** is recommended to host both repos and enable cleaner access control, team collaboration, and branding. See [GitHub's guidance on Organizations](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations).
13
13
14
14
---
15
15
@@ -54,16 +54,16 @@ LAF-PRIVATE/
54
54
55
55
### Step 1: Create a GitHub Organization (optional but recommended)
56
56
57
-
1. Go to [github.com/organizations/new](https://github.com/organizations/new) and create a free organization (e.g., `LAF-org` or `loganfinney27-projects`).
57
+
1. Go to [github.com/organizations/new](https://github.com/organizations/new) and create a free organization named **`LAF-US`**.
58
58
2. Transfer ownership of existing repos to the org, or create the new consolidated repos directly under the org.
59
59
60
60
> **Why an Organization?** Organizations allow granular team permissions, separate billing, and a professional namespace. All repos remain under your control. See the [community discussion](https://github.com/orgs/community/discussions/143759) for more context.
61
61
62
62
### Step 2: Create the LAF-PUBLIC repository
63
63
64
64
```bash
65
-
# On GitHub.com (or via gh CLI):
66
-
gh repo create LAF-PUBLIC --public --description "All public-facing LAF projects"
65
+
# On GitHub.com (or via gh CLI) — create under the LAF-US organization:
66
+
gh repo create LAF-US/LAF-PUBLIC --public --description "All public-facing LAF projects"
67
67
```
68
68
69
69
### Step 3: Migrate each public repo into LAF-PUBLIC as a subdirectory
@@ -72,7 +72,7 @@ Use `git subtree` to preserve commit history for each project:
0 commit comments