Skip to content

Fix: Step 1 clone layout so cd targets the sibling clone - #39

Open
aslom wants to merge 1 commit into
rossoctl:mainfrom
aslom:fix_step1_clone_layout
Open

Fix: Step 1 clone layout so cd targets the sibling clone#39
aslom wants to merge 1 commit into
rossoctl:mainfrom
aslom:fix_step1_clone_layout

Conversation

@aslom

@aslom aslom commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Split the combined mkdir -p ... && cd ... into two lines and change the post-clone cd "$HOME/rossoctl-src/rossoctl-cli" to a relative cd rossoctl-cli. Since the clones now run from inside $HOME/rossoctl-src, the relative cd lands in the just-created clone and stays consistent with the sibling ../cortex replace path, whichever scratch dir the reader used.

Addresses the Step 1 finding in #35.

Fixes: #35

Assisted-By: Claude (Anthropic AI) noreply@anthropic.com

Summary

Related issue(s)

(Optional) Testing Instructions

Fixes #

Split the combined `mkdir -p ... && cd ...` into two lines and change the
post-clone `cd "$HOME/rossoctl-src/rossoctl-cli"` to a relative `cd rossoctl-cli`.
Since the clones now run from inside $HOME/rossoctl-src, the relative cd lands in
the just-created clone and stays consistent with the sibling `../cortex` replace
path, whichever scratch dir the reader used.

Addresses the Step 1 finding in rossoctl#35.

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Aleksander Slominski <aslom@us.ibm.com>
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.

Fix: Step 1 cd target and agent.sh asset path break real setup flow

1 participant