Skip to content

feat: Clone existing repository config - #907

Open
alyssaholland99 wants to merge 1 commit into
garethgeorge:mainfrom
alyssaholland99:feat-clone_repositories
Open

feat: Clone existing repository config#907
alyssaholland99 wants to merge 1 commit into
garethgeorge:mainfrom
alyssaholland99:feat-clone_repositories

Conversation

@alyssaholland99

@alyssaholland99 alyssaholland99 commented Sep 18, 2025

Copy link
Copy Markdown

Added a button to clone existing repository configs. This preserves everything about the repository config you're trying to clone, while all fields remain editable, allowing you to use the same settings for different repositories.

@alyssaholland99

Copy link
Copy Markdown
Author

Repository config to clone, notice the new "Clone Repository Config" button.

Initial_Repository_To_Clone

Modal shown after the 'Clone Repository Config' button is clicked

Cloned_Repository_Config

Cloned repository config saved successfully

Cloned_Repository_Saved

@alyssaholland99

Copy link
Copy Markdown
Author

@garethgeorge The PRs I've put up should be ready for review if you have the time :)

@garethgeorge

Copy link
Copy Markdown
Owner

Hi -- thanks for the interest in contributing, appreciate the PR! I want to start out with this is definitely a long standing issue and something I'd like to address, but I'm a bit opinionated about the right way to solve this.

I'm hesitant to introduce a new button on the submit rows of the repo / plan UIs since they'll become cluttered, duplicating plans or copying configuration is only something we think about when making a new plan or repo.

My thinking for a good solution to this is that it should be something like an optional dropdown when creating a new plan or repo (from an empty state) which allows the user to copy settings from an existing plan / repo.

wdyt?

@alyssaholland99

Copy link
Copy Markdown
Author

Oh that's a good idea - I'll look at implementing this both on this PR and on the plan PR :)

@seb26

seb26 commented Jan 13, 2026

Copy link
Copy Markdown

@garethgeorge

It's a more common UI trope to visit the 'one' you want to duplicate, to duplicate it

Of course 'Add Plan' | 'Add Plan from Existing' might be OK, but you suggest a dropdown or an arrow, that is now way more involved or prominent in the UI flow than a 'Duplicate' button

And if the 'Add Plan' blank window suggests to pull in config from another plan, then you have to have UI to permit selection of which plan, ... that's extra steps...

I think simplest most intuitive option wins out here...

I'm hesitant to introduce a new button on the submit rows of the repo / plan UIs since they'll become cluttered

This can be addressed here by just using the button label "Duplicate" instead of the PR's suggestion "Clone Repository Config"

which unnecessarily repeats the modal context 'repository config', among neighbouring buttons which do not do this (e.g. 'Delete' not 'Delete Repository')

There are not many other possible buttons to add here, either, so the clutter isn't already happening nor likely to

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.

3 participants