Closed Bug 1923189 Opened 1 year ago Closed 1 year ago

Request for GitHub Organization Access to Mozilla Services

Categories

(mozilla.org :: Github: Administration, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sykim, Assigned: cknowles)

Details

Hi, I need access to mozilla-services as a new member of the Autograph team. Thank you!

I approve of this PR!

We were under the impression she had her account there already as she's been able to be added to teams. But she can't find an invite link that would have matched. She was added to the org perhaps so long ago that some other perms that should have been provided weren't? She's been unable to push to repos she has write access to.

She is already a member of the org - and a member of the autograph-mergers team - is there a specific team that is missing?

There's

Jeff - afaict, you're a maintainer of all these teams - so your say so is more than sufficient - but she's also a member of the org, so you can add to any of these teams as well.

Let us know, we're happy to help.

Assignee: nobody → cknowles
Flags: needinfo?(jehodges)

Well, she's not able to clone any private repos from her machine in the mozilla-services organization nor push branches to the same even when she has the rights to. She's able to do both those things with the mozilla organization repos.

Flags: needinfo?(jehodges)

She's ostensibly added the mozilla-services org to her github key (we can see that in the github UI). We're going to try a new ssh key and hope something was just hinky with the old one.

Yes, likely because she's not a member of the right team(s) or repos ... is there a list of repos that she's wanting write access to? (clone is read access, but push would be write access.). From that I can probably advise on teams/next-steps.

<just saw your update about tokens>

And looking at her existing team of autograph-mergers - that does give write access to several of the autograph repos.

One thing to check is that any personal access token or keys are authorized to work with our SAML'd orgs - https://wiki.mozilla.org/GitHub/GHE_SAML_User_FAQ#Authorize_PAT_.28Personal_Access_Tokens.29

Okay, oddly enough her ssh key (which seems totally valid and works for other repos and for which she had authorized) didn't work but with a new ssh key it worked fine. She did change the email address in the pub key half, but that seems irrelevant. The authorizations were the same on both ssh keys. Really baffling.

Thanks for your patience with us!

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.