Support project export for eclipselabs.org about support-tools HOT 21 CLOSED

Issue 17 has been merged into this issue.

I've my project under "https://code.google.com/a/eclipselabs.org/p/logviewer/" 
and there is a button "Export to GitHub". The process can be started and also 
there is new repo "https://github.com/anb0s/logviewer" with one initial commit 
and email message about "Export Complete".

@andr: That's because there is a project called logviewer in the default (not 
eclipselabs.org) namespace: https://code.google.com/p/logviewer - it was 
converted instead of yours.

Issue 38 has been merged into this issue.

@harmathdenes: thanks for the info! so export from eclipselabs.org is not 
possible.
I've deleted the wrong imported project "https://github.com/anb0s/logviewer" 
and created one with different name 
"https://github.com/anb0s/eclipse-logviewer" for my experiments with manual 
migration (https://code.google.com/p/support-tools/wiki/MigratingToGitHub).

So if export from eclipselabs.org will be supported i will try it again...

code import was easy, but issues are not possible, because Google Takeout is 
not available for me :( need the automatic solution for eclipselabs.org export 
to GitHub...

Issue 53 has been merged into this issue.

Until this is resolved, the Export to GitHub button should be disabled because 
it exports the wron project!

What about this feature now? It was promised for the week from 16th of March in 
Issue 38. Can you give a rough estimation?

Sorry for the delay in getting this feature out there, unfortunately I've been 
swamped. I can confirm that I've started and have the first 90% finished... but 
I don't know how long until I get the _next_ 90% finished and rolled out. [1]

In the mean time, you can use our stand-alone tools for exporting your project 
to GitHub. Though I don't think it will take much more than a few more weeks.

[1] http://en.wikipedia.org/wiki/Ninety-ninety_rule

@Chris: Thanks for the status update! What exactly are the "stand-alone" tools 
you are mentioning?

This has been fixed and rolled out. To export a project from eclipse-labs, add 
"eclipselabs.org:" as a prefix to the project name. For example, to export:
https://code.google.com/a/eclipselabs.org/p/cppcheclipse/

Enter "eclipselabs.org:cppcheclipse" as the project name.

As for the "stand-alone" tools, I was referring to the tools mentioned in this 
wiki post:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Could you fix the parametrisation of the GitHub exporter? Currently when 
clicking on "Export to Github" on 
https://code.google.com/a/eclipselabs.org/p/cppcheclipse/ the wrong project is 
gonna be exported and there is no possibility to set a prefix (the link 
https://code.google.com/export-to-github/export?project=cppcheclipse seems to 
be wrong). Only when the exporter is called manually via 
https://code.google.com/export-to-github/ it is possible to enter a prefix.

@konrad_w, good catch! I'll work on fixing that next. Sorry about the bug!

thanks, i've successfully exportet the project 
"https://code.google.com/a/eclipselabs.org/p/logviewer/" to GitHub!

In my case (eclipselabs.org project Fastest) I was able to start the export, 
but the importer fails with error message: "There was an error pushing commits 
to GitHub."
I have tried to restart the import process several times but it still fails 
with the same error.
Any ideas?

Thanks

Re: "There was an error pushing commits to GitHub."

Unfortunately that error message is all we get, so I can't help you in 
diagnosing the problem. However, our colleagues at GitHub suggest that we ask 
people to contact GitHub's support at "https://github.com/contact". Please 
include the name of the target repository (e.g. https://github.com/user/repo), 
and they will be able to assist you from there.

FYI I was getting the error during import because my SVN repository contains a 
file larger than 100MB. There is a 100MB per file limit at GitHub.
They have sent me a guide explaining how to clean up the repository before 
importing.

Thanks again.