colcon-cargo repository

[lelongg]

Just to notify that I worked on a colcon extension to build Rust projects with Cargo.
You may want to add it to this organization.

https://github.com/lelongg/colcon-cargo

[dirk-thomas]

In order to move it to the colcon org unit we can do either of the following:

• You transfer to repo to the colcon org unit (I hope that works without permissions), I give you admin access to the moved repo afterwards.

• I created a new repo, give you admin access to it and you push the same content to it. Afterwards you could remove your repo.

[lelongg]

I tried to transfer it but got a permission error.
I'm ok with plan B.

[dirk-thomas]

Let's try plan C first 😉 Can you give me admin access to the repo and I can try to move it?

[lelongg]

Invite sent

[dirk-thomas]

It seems to only grant push access but not admin. (Maybe not possible for user repos?)

Back to plan B I guess...

[dirk-thomas]

With no tickets to migrate and only a single branch plan B is just fine: https://github.com/colcon/colcon-cargo I also send you an invite for it.

[dirk-thomas]

You will just need to setup the Travis / AppVeyor integration again.

[lelongg]

Everything seems fine. AppVeyor is enabled and Travis should soon.

[tfoote]

For future reference the only effective way I've found to transfer from a personal account to an organization with limited permissions is for the origin user to transfer it to the admin users's personal account and then the admin user transfers it to the organization. Github will track the double redirect and everything keeps working as long as the admin user and the origin user don't refork the repository into their accounts.