Skip to content

gh repo create does not respect organization name when instantiating repo #3918

@larsvilhuber

Description

@larsvilhuber

Describe the bug

When attempting to create a repo in an organization's (rather than personal) space, gh goes through the right prompts, but then ignores the organization, creating a repo in the personal space.

gh version 1.12.0 (2021-06-29)
https://github.com/cli/cli/releases/tag/v1.12.0

Steps to reproduce the behavior

  1. Run gh repo create (orgname)/reponame
  2. Answer all the prompts however you want
  3. Observe the reported reponame, and verify in Github.com space.

Expected vs actual behavior

Expected behavior: Create repo "(organization)/(reponame)"

Actual behavior: Confirms to user that will create "(organization)/(reponame)" but then actually creates (and reports creation) of "(personal)/reponame".

Logs

gh repo create AEADataEditor/editor-scripts
? Visibility Public
? Would you like to add a .gitignore? Yes
? Choose a .gitignore template TeX
? Would you like to add a license? Yes
? Choose a license BSD 3-Clause "New" or "Revised" License
? This will create the "AEADataEditor/editor-scripts" repository on GitHub. Continue? Yes
Created repository larsvilhuber/editor-scripts on GitHub
? Clone the remote project directory "larsvilhuber/editor-scripts"? Yes

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingmore-info-neededMore info needed from user/contributorpriority-2Affects more than a few users but doesn't prevent core functions

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions