Skip to content

Clarify repo-create confirmation prompt#2507

Closed
nilsvu wants to merge 1 commit intocli:trunkfrom
nilsvu:patch-2
Closed

Clarify repo-create confirmation prompt#2507
nilsvu wants to merge 1 commit intocli:trunkfrom
nilsvu:patch-2

Conversation

@nilsvu
Copy link
Contributor

@nilsvu nilsvu commented Nov 29, 2020

When I read the message I thought the command would create a new directory for the new repository in my current directory. I think the message should make clear that no new directory is created, but the new GitHub repository is added as remote origin to the current directory's git repo.

If anyone has better suggestions for formulating this in a concise way, I'm happy to change the wording in this PR.

promptString = fmt.Sprintf("This will create '%s/%s' and add it as remote for your current directory. Continue? ", repoOwner, repoName)
} else {
promptString = fmt.Sprintf("This will create '%s' in your current directory. Continue? ", repoName)
promptString = fmt.Sprintf("This will create '%s' and add it as remote for your current directory. Continue? ", repoName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error message will be accurate for the mode when repo create is running within the context of a git repo, but will not be accurate when repo create is running outside of a local git repo. In the latter case, there will be an additional prompt to optionally clone the new repository in a subdirectory. See #1913

I'm not sure what the solution should be. Please let us discuss this with our team first and get back to you. 🙇

@vilmibm
Copy link
Contributor

vilmibm commented Jan 21, 2021

Thanks for this! We're planning a full overhaul of the repo create command, so we're closing these more piecemeal improvements.

@vilmibm vilmibm closed this Jan 21, 2021
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