Creating private repository for organization uses default team #249

Closed
calebthompson opened this Issue Oct 23, 2012 · 5 comments

Comments

Projects
None yet
3 participants
@calebthompson
Contributor

calebthompson commented Oct 23, 2012

I ran the following command twice, and got some unexpected results.

hireling[master]/
↪ git create -p organization/repository
Updating origin
ERROR: Repository not found.
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
hireling[master]/
↪ git create -p organization/repository
Error creating repository: Unprocessable Entity (HTTP 422)
name already exists on this account

It turns out that the repository was created, but private to the organization's default team (of which I am not a part). It seems acceptable if I were part of the organization, but odd that I can create a repository which I do not have access to.

@mislav

This comment has been minimized.

Show comment Hide comment
@mislav

mislav Nov 5, 2012

Member

Weird. Definitely you should report to GitHub (API bug)

What you'd want here is a way to specify the team on command-line; is that right?

Member

mislav commented Nov 5, 2012

Weird. Definitely you should report to GitHub (API bug)

What you'd want here is a way to specify the team on command-line; is that right?

@calebthompson

This comment has been minimized.

Show comment Hide comment
@calebthompson

calebthompson Nov 5, 2012

Contributor

Specifying team would be an acceptable workaround, but it would be even nicer if the API figured out that I was on a team and gave that team permissions.

Would you suggest just hitting up support@github.com about this?

Contributor

calebthompson commented Nov 5, 2012

Specifying team would be an acceptable workaround, but it would be even nicer if the API figured out that I was on a team and gave that team permissions.

Would you suggest just hitting up support@github.com about this?

@mislav

This comment has been minimized.

Show comment Hide comment
@mislav

mislav Nov 5, 2012

Member

Would you suggest just hitting up support@github.com about this?

Definitely ask them why are you able to create a repo on a team which you don't belong to.

Member

mislav commented Nov 5, 2012

Would you suggest just hitting up support@github.com about this?

Definitely ask them why are you able to create a repo on a team which you don't belong to.

@praseodym

This comment has been minimized.

Show comment Hide comment
@praseodym

praseodym Feb 8, 2013

Just hit this same bug; already sent off a mail to support because I figured this would be a bug in the API. It's super-irritating because I want to move a bunch of repos to Github and really don't want to create them manually.

Just hit this same bug; already sent off a mail to support because I figured this would be a bug in the API. It's super-irritating because I want to move a bunch of repos to Github and really don't want to create them manually.

@mislav

This comment has been minimized.

Show comment Hide comment
@mislav

mislav Jul 26, 2014

Member

Closing this in favor of #431 which indicates that team_id is now required parameter. Hub needs to be expanded to support that, but unfortunately isn't yet.

Member

mislav commented Jul 26, 2014

Closing this in favor of #431 which indicates that team_id is now required parameter. Hub needs to be expanded to support that, but unfortunately isn't yet.

@mislav mislav closed this Jul 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment