justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(blog): fill course-link placeholders + align learner-dir path

Browse Source 
- Replace all 24 [COURSE LINK] placeholders across the 17 posts with the course URL
  https://git.jpaul.io/justin/ai-workflow-course.
- Align the learner working-dir path in the posts to ~/ai-workflow-course (matches
  the modules after the repo rename).
- blog/README: mark the course-link checklist item done; flag publish-time
  refinements (GitHub-mirror swap; repoint inline cross-post links to real
  jpaul.me post URLs).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
This commit is contained in:
Claude (agent)
2026-06-22 19:15:20 -04:00
parent e5960c17ab
commit 250189a60e
18 changed files with 41 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
blog/09-remotes-and-hosting.md
+3 -3
View File
@@ -15,7 +15,7 @@ I run my own Git forge. Not GitHub — an actual server I keep at `git.jpaul.io`
I'm telling you that up front not to flex, but because this post is the one where I'm most in my own wheelhouse, and I want you to know the punchline before I prove it: **it does not matter where you push.** GitHub, GitLab, a box in my closet — the commands are identical, and the reason they're identical is the whole lesson.
This post opens Unit 2 of [The Workflow]([COURSE LINK]) — the team layer. Up to now the course has been about getting *you* and your AI working safely on one machine: version control as undo, the AI editing real files, your config committed as a durable artifact. All of that lives on one disk. This module gets it *off* that disk. If you've been following along, this is the moment the safety net stops being local.
This post opens Unit 2 of [The Workflow](https://git.jpaul.io/justin/ai-workflow-course) — the team layer. Up to now the course has been about getting *you* and your AI working safely on one machine: version control as undo, the AI editing real files, your config committed as a durable artifact. All of that lives on one disk. This module gets it *off* that disk. If you've been following along, this is the moment the safety net stops being local.
## A remote is just another copy
@@ -42,7 +42,7 @@ git clone <URL> # make a brand-new local copy, full history and al
The one thing those commands assume is that a remote repo *exists* to push into. On every host the shape is identical: in the web UI, create a **new, empty** repository — do **not** let it add a README, license, or `.gitignore`, because you want your local history to be the first thing that lands in it. Copy the URL it hands you (HTTPS or SSH), then:
```bash
cd ~/workflow-course/tasks-app
cd ~/ai-workflow-course/tasks-app
git remote add origin <URL-you-copied>
git push -u origin main
```
@@ -103,7 +103,7 @@ A four-person team pushing to one remote is sitting on five-plus complete, indep
You can watch it happen with your own eyes in the lab. Push your `tasks-app`, then clone it into a separate directory as if you were a teammate on a fresh machine, and count the commits in each:
```bash
cd ~/workflow-course
cd ~/ai-workflow-course
git clone <URL> tasks-app-teammate
cd tasks-app-teammate
git log --oneline | wc -l # compare to your original repo — they match