Hi, Just changed the base member permission to write, that should solve your problem. Can you confirm that?
BR Zahed On 2019-03-06, 13:29, "Taps on behalf of Theresa Enghardt" <[email protected]<mailto:[email protected]> on behalf of [email protected]<mailto:[email protected]>> wrote: Thanks for migrating the repo! On Mar 5, 2019, at 2:06 PM, Brian Trammell (IETF) <[email protected]><mailto:[email protected]> wrote: CircleCI support for autobuilding drafts should be up sometime tomorrow (it's late here); please let me know if you notice any problems with the migration. Not sure if problem or intended, but: As a member of the organization, I used to be allowed to create and push branches directly to the api-drafts repository. However, on the new organization, this did not work just now, see below. Is this intentional, in which case I will just fork the repo and push the branch there? Or is this a bug in the configuration of the new organization? --- $ git push -u origin theri-api-usage-example ERROR: Permission to ietf-tapswg/api-drafts.git denied to theri. fatal: Konnte nicht vom Remote-Repository lesen. Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen und das Repository existiert. $ git remote -v origin [email protected]:ietf-tapswg/api-drafts<mailto:[email protected]:ietf-tapswg/api-drafts> (fetch) origin [email protected]:ietf-tapswg/api-drafts<mailto:[email protected]:ietf-tapswg/api-drafts> (push) -- (It says that it could not read from the remote repository and that I should check if I have the correct permissions and that the repository exists.) Cloning the entire repository again in a different directory did not help. "git pull" works as usual. Best, Theresa
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
