Skip to content

Refactors initialization to use direct clone flow#22

Merged
aboo merged 1 commit into
mainfrom
feature/pap-7027-refactor-initialisation
Apr 10, 2026
Merged

Refactors initialization to use direct clone flow#22
aboo merged 1 commit into
mainfrom
feature/pap-7027-refactor-initialisation

Conversation

@aboo
Copy link
Copy Markdown
Contributor

@aboo aboo commented Apr 10, 2026

What does this PR do?

Replaces the previous fork-based initialization with a more flexible direct cloning mechanism. Users can now specify a source repository to clone from and optionally create a private GitHub repository, setting it as the origin remote. This change removes the --no-fork flag and introduces --source and --remote flags, updating both interactive (TUI) and non-interactive flows to support these new options.

Relates to PAP-7027

- Removes forking to avoid exposing private submodule
  references in public forks
- Adds --source flag (default: plan-and-publish/workbench)
  and --remote flag for optional private repo creation
- Removes --no-fork flag and forkRepo/executeFork entirely
- Adds new TUI screens: source input, remote prompt, remote
  name input
- Removes origin remote after clone; optionally creates
  private GitHub repo as origin

Delivers PAP-7027
@aboo aboo merged commit 9eeed74 into main Apr 10, 2026
1 check passed
@aboo aboo deleted the feature/pap-7027-refactor-initialisation branch April 10, 2026 05:06
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