Skip to content

fix(install): point REPO_URL at this repo + unmute clone errors#39

Open
reikjarloekl wants to merge 1 commit into
AgriciDaniel:mainfrom
reikjarloekl:fix/install-repo-url
Open

fix(install): point REPO_URL at this repo + unmute clone errors#39
reikjarloekl wants to merge 1 commit into
AgriciDaniel:mainfrom
reikjarloekl:fix/install-repo-url

Conversation

@reikjarloekl

Copy link
Copy Markdown

Summary

  • install.sh's REPO_URL still pointed at https://github.com/AI-Marketing-Hub/claude-ads, which no longer resolves. Anyone running bash install.sh (including via the documented "clone + bash install.sh" pattern) currently hits a silent exit 128.
  • Updated REPO_URL to point at https://github.com/AgriciDaniel/claude-ads.
  • Removed 2>/dev/null on the clone — that's what hid the underlying remote: Repository not found. message and made the failure look like a generic git error with no explanation. Errors on this line are always actionable and belong on stderr.

Reproduction (before this PR)

$ git clone --depth 1 https://github.com/AgriciDaniel/claude-ads /tmp/claude-ads && cd /tmp/claude-ads && bash install.sh
...
✓ Git detected
↓ Downloading Claude Ads...
$ echo $?
128

With 2>/dev/null removed, the real error becomes visible:

remote: Repository not found.
fatal: repository 'https://github.com/AI-Marketing-Hub/claude-ads/' not found

After this PR

Verified end-to-end in a clean debian:bookworm-slim container — install.sh completes with exit 0 and lays down all 22 sub-skills and 10 agents.

Test plan

  • bash install.sh succeeds in a fresh container with only git + ca-certificates
  • Diff is two lines, both in install.sh; no behavior change to any other target/path

…one errors

install.sh's REPO_URL still pointed at https://github.com/AI-Marketing-Hub/claude-ads,
which no longer resolves ("Repository not found"). That made `bash install.sh`
fail with exit 128 for everyone whose Dockerfile/script does the documented
two-step (clone this repo + run install.sh), because install.sh re-clones the
repo from REPO_URL rather than reusing the already-cloned checkout.

Also drop `2>/dev/null` on the clone — it was what masked the real
"Repository not found" message and made the failure look like a generic
exit 128 with no explanation. Errors on this line are always actionable;
they belong on stderr.

Verified end-to-end in a clean debian:bookworm-slim container: install
completes with exit 0 and lays down all 22 sub-skills and 10 agents.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant