I don't have permission to push on repo created by me #123

Closed
rafaelbco opened this Issue Jan 12, 2012 · 12 comments

Projects

None yet

6 participants

@rafaelbco
Contributor

Hi,

I edited permissions.cfg and added myself to the contributors team and the following repo:

[repo:collective.anotherdynamicgroupsplugin]
fork = rafaelbco/collective.anotherdynamicgroupsplugin
teams = contributors
owners = rafaelbco

Now the changes to permissions.cfg were merged. However I don't have permission to push to "collective.anotherdynamicgroupsplugin". It seems I have permission to push to all other repos in the collective organization though.

@jensens
Member
jensens commented Jan 16, 2012

Rok, can you please look at this one too?

@garbas garbas was assigned Jan 16, 2012
@claytron
Member

I have a similar issue for the collective.bpzope repo that was just created. I don't have admin rights to it and I can't push code either.

@malthe
Member
malthe commented Jan 17, 2012

Same here.

@claytron
Member

I spoke to @garbas on IRC and he said there is an issue with the script right now. He is busy finishing up a project, but will try to look into it soon (he did not have an ETA).

Does anyone else have access to debug the script that runs the sync?

@aclark4life
Member

Do all of these issues apply to forked repos only? If so, then one potential work around is to create a new repo instead. I've never had any trouble doing that FWIW. That said, seems like we could use a few more org admins to resolve issues as needed (i.e. when garbas is unavailable.)

@malthe
Member
malthe commented Jan 17, 2012

This was a newly created repository for me.

@rafaelbco
Contributor

Is it possible to fix it manually for now ?

On Tuesday, January 17, 2012, Malthe Borch <
reply@reply.github.com>
wrote:

This was a newly created repository for me.


Reply to this email directly or view it on GitHub:

#123 (comment)

Rafael Bruno Cavalhero de Oliveira
Analista de Desenvolvimento de Sistemas - SERPRO
http://rafaelb.objectis.net

@aclark4life
Member

Yes, assuming @garbas fixes it or gives someone else permissions to fix it

@garbas
Contributor
garbas commented Jan 18, 2012

hey guys ... i'll try to find time today to give it a look .. for now use your own account and you'll push code back when this issues are solved

@garbas
Contributor
garbas commented Jan 18, 2012

this should be fixed now

@garbas garbas closed this Jan 18, 2012
@claytron
Member

Works for me now. Thanks @garbas!

@rafaelbco
Contributor

Works for me too, thanks.

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