| [keti-dev] Keti initial contribution - git repo |
| I’m following up on Anubhav’s request on IPzilla here on the mailing list, as this is information that might be useful for others. The request was: "I've checked in our code to http://git.eclipse.org/c/gerrit/www.eclipse.org/keti.git/ however it seems like we don't have permission to force-push to the master branch so I had to resort to adding another commit on top of the initial one by the webmaster. I was attempting to follow instructions similar to what's described in https://wiki.eclipse.org/GitHub but maybe the master branch is protected? Also the git.eclipse.org commits don't seem to be mirrored to https://github.com/eclipse/keti . I couldn't find the "official" GitHub mirroring process in the Eclipse docs beyond what's covered in https://wiki.eclipse.org/Git so maybe one of you guys can shed some light on the actual process for mirroring to our repo under the eclipse public GitHub org?" The http://git.eclipse.org/c/gerrit/www.eclipse.org/keti.git repo is actually meant to be the Keti *website* content, i.e whatever you will be pushing there is effectively what will be served on http://eclipse.org/keti - see e.g http://git.eclipse.org/c/gerrit/www.eclipse.org/californium.git/tree/ for the Eclipse Californium website. It is intentional that force push is not enabled, as it is expected people commit/rebase on top of the webmaster’s initial commit. As far as getting the actual Keti code contributed to https://github.com/eclipse/keti, which is the repo for the code, have all the Keti committers filled in their Github ID in the eclipse portal? This is how webmaster can provide write access to the commiter's Github accounts. Hope this helps, Benjamin - |
Attachment:
signature.asc
Description: Message signed with OpenPGP