gh repo create: when adding a team, the granted permission is "read"?

[ecs-hk]

Given the following:

gh repo create someorg/myrepo \
        --add-readme \
        --team='goodguys' \
        --internal

• "myrepo" is successfully created within "someorg"
• The (already existing) "goodguys" team is added with Role:read

But I need "goodguys" to have Role:maintain access. How can this be accomplished?

The gh repo command does not appear to support adding a team with anything other than Role:read.
I tinkered with gh api but did not find a way to update the role/permissions for a team.

[mislav]

Hi, this is a popular request, but changing the role at gh repo create time for now isn't possible. Please follow #2241 for updates

[ecs-hk]

Thanks for the reply. I will follow that issue. I noticed one line of interest in your gh-repo-collab code:

gh api --method=PUT "orgs/${repo%/*}/teams/${user#*/}/repos/$repo" "${args[@]}"
# ^^ line 88, as of this writing..

So after repo creation, I was hoping I could call this like:

gh api -X PUT 'orgs/someorg/teams/goodguys/repos/myrepo' \
        -f 'permission=maintain'

(I think that matches the pattern I see in your code, but when I attempt it the response is HTTP 404.)

---

Ah, never mind. I have resolved this problem by adding the org prior to the repo in the path, a la:

gh api -X PUT '/orgs/someorg/teams/goodguys/repos/someorg/myrepo' \
        -f 'permission=maintain'

And now it is doing exactly what I want. I can simply perform the following:

1. Create a new repo with gh repo create
2. Add a team with maintain permission using the gh api instruction above

Shall I add this workaround to the issue you referred to above? I would think other CLI/API consumers are in a similar situation as me, i.e. they would like to get this end state even if it requires two separate calls.

[mislav]

Yes please! Thanks for coming up with a workaround and you should add it to the referenced issue. Maybe we could change gh repo create --team to do this automatically.