Skip to content

Commit efe85a3

Browse files
Update MIGRATION.md to use LAF-US as the GitHub Organization name
Agent-Logs-Url: https://github.com/loganfinney27/PyTutorial/sessions/ac28e224-84ad-4846-a8b1-da3096a92271 Co-authored-by: loganfinney27 <136375980+loganfinney27@users.noreply.github.com>
1 parent 872c720 commit efe85a3

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

MIGRATION.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Logan currently has several scattered public repositories. The goal is to consol
99
| **LAF-PUBLIC** | All publicly shareable projects and work |
1010
| **LAF-PRIVATE** | Private, sensitive, or work-in-progress content |
1111

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).
1313

1414
---
1515

@@ -54,16 +54,16 @@ LAF-PRIVATE/
5454

5555
### Step 1: Create a GitHub Organization (optional but recommended)
5656

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`**.
5858
2. Transfer ownership of existing repos to the org, or create the new consolidated repos directly under the org.
5959

6060
> **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.
6161
6262
### Step 2: Create the LAF-PUBLIC repository
6363

6464
```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"
6767
```
6868

6969
### 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:
7272

7373
```bash
7474
# Clone the new empty LAF-PUBLIC repo
75-
git clone https://github.com/<your-username-or-org>/LAF-PUBLIC.git
75+
git clone https://github.com/LAF-US/LAF-PUBLIC.git
7676
cd LAF-PUBLIC
7777

7878
# Add each existing repo as a remote and merge it into a subdirectory
@@ -97,7 +97,7 @@ git commit -m "chore: migrate PyTutorial into py-tutorial/"
9797
### Step 4: Create the LAF-PRIVATE repository
9898

9999
```bash
100-
gh repo create LAF-PRIVATE --private --description "Private LAF projects and archives"
100+
gh repo create LAF-US/LAF-PRIVATE --private --description "Private LAF projects and archives"
101101
```
102102

103103
Then migrate IDAHO-VAULT into `idaho-vault/` using the same `git subtree` approach.
@@ -118,7 +118,7 @@ Once migration is complete and verified:
118118

119119
## Checklist
120120

121-
- [ ] Create GitHub Organization (optional)
121+
- [ ] Create GitHub Organization **LAF-US**
122122
- [ ] Create `LAF-PUBLIC` repo (public)
123123
- [ ] Migrate `loganfinney27.github.io``LAF-PUBLIC/github-pages/`
124124
- [ ] Migrate `THE-GEMSTONE``LAF-PUBLIC/the-gemstone/`

0 commit comments

Comments
 (0)