mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
The quick start walked a new user into gh repo fork - forks of public repos are always public - and two steps later had /setup write personal data into tracked files, with the only complete warning in SETUP.md section 8, a section about pulling updates that a first-time user has no reason to open during onboarding. A real user hit exactly this (#345). The warning now sits adjacent to both fork commands (README step 1, SETUP.md section 2, both pointing at section 8's private-remote recipe), and /setup checks the origin's visibility BEFORE writing anything: a public-fork origin gets a confirm-first warning instead of a note after every file is on disk. A private origin, no origin, or a non-git directory continues silently. Reported by @basilevs with a complete reproduction and fix analysis; this implements his fixes (1) and (4). Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
ab5d23bad4
commit
34b8b3f91f
@@ -78,6 +78,15 @@ gh repo fork MadsLorentzen/ai-job-search --clone
|
||||
cd ai-job-search
|
||||
```
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **A fork of this repo is always public** — GitHub does not allow private forks of
|
||||
> public repositories — and `/setup` (step 3 below) writes your personal data (name,
|
||||
> contact details, employment history, salary expectations) into **tracked** files.
|
||||
> If this copy is for your own job search rather than for contributing changes back,
|
||||
> use a **private repository** with this repo as `upstream` instead — the two-minute
|
||||
> recipe is in [SETUP.md section 8](SETUP.md#8-pulling-upstream-updates-into-your-fork),
|
||||
> and every update workflow works identically. Fork only to contribute.
|
||||
|
||||
### 2. Install job search tools
|
||||
|
||||
PowerShell:
|
||||
|
||||
Reference in New Issue
Block a user