Github To Eclipse


First, on GitHub, create an empty Repository with any name, but it is highly recommended to name it after your Java project on Eclipse. How to create and delete a Repository on GitHub? Next, on Eclipse, create a project named MyJavaProject. Clone /fork an existing project from GitHub and import it into Eclipse. Part 4: Use EGit to track a change In the ' Git Repositories' window, right-click on the rr- eclipse - git project and select ' Pull '. In the Eclipse 'Project Explorer' on the left, expand the rr- eclipse - git project and double-click on the file 'names.

  • Navigation
  • Main Page
  • Community portal
  • Current events
  • Recent changes
  • Random page
  • Help
  • Toolbox
  • Page information
  • Permanent link
  • Printable version
  • Special pages
  • Related changes
  • What links here

This page details the required actions to migrating a repo to Eclipse Foundation GitHub followed by the Webmaster team.

Import Github To Eclipse

  • 1Migrating a GitHub repo to Eclipse Foundation GitHub organization
  • 2End User required actions

Migrating a GitHub repo to Eclipse Foundation GitHub organization

Step 0 - Transfer repo from original location to Eclipse Foundation Organization

  • Make sure IP team has cleared the Initial contribution, and project has TAGged the initial contribution in the repo
  • Transfer the repo

Step 1 - Create new branches and tags with namespace /_old/

Since the Eclipse IP team does not perform a code review on historical code, we must move history to a different namespace. This will allow the Eclipse Foundation to maintain a mirror of the GitHub repository on its servers, without the historical content.

Below, URL implies the SSH url that you can (eventually) push back to.

Replace URL with the repository location on GitHub.

Step 2 - Delete old branches and tags that were renamed

Upload to github eclipse

Move your backup clone aside, then re-clone the repo from GitHub.

You'll probably get an error. It is expected.

Deleting master branch will fail because it's the current branch.

If you get errors like 'dst refspec <branch> matches more than one' when deleting branches you may have a tag which has the same name as a branch. You can delete the branch like this:

Step 3 - Push a new Eclipse Approved master

If the project hasn't already squashed history, and master contains an unmodified copy of the initial contribution:

Github To Eclipse

If an initial contribution tag was created(and histroy squashed):

If an initial contribution tag was created, but the history hasn't been squashed

Step 4 - refs replace

If you'd like the 'full' history in your local clone.

Grab refspec for new and old commit

  • NOTE: End user must additionally run (if they want the history): git fetch origin '+refs/replace/*:refs/replace/*'

At this point, clone from the GitHub location just to see if everything is there. But otherwise, the repo is done and historical content is all in _old/.

Import Project From Github To Eclipse

End User required actions

If a user had previously cloned the repository before it was moved to the Eclipse Foundation GitHub organization, the move will have caused a few issues to the user’s local repository. The easiest option to resolve the issues is to just do a brand new git clone of the repository from the new location. If however this is not an option below outlines issues that the user will run into and steps to resolve the issues.

Fix master branch

The user’s master branch will still be based on the old master branch and needs to be changed to the new master.

The following commands will rename the local master to “old_master” and create a new master based on the new upstream master:

Repeat these steps for any other additional branches that may have conflict.

(Optional) Git Replace history

If the user would like to see the old history attached to the new Initial Commit they can checkout the refs/replace/* refspec.

Forked repositories

Forked repositories will have branches that no longer match with upstream due to upstream renaming all the branches to /_old/ prefix. The easiest way to resolve this issue is to refork upstream. However if this is not an option below lists the tasks that will need to be considered in each fork of the project.

Fix master branch

Eclipse Connect To Github

The fork’s master branch and upstream master branches will be different. To fix this the fork owner can rename their original master branch and push a new master branch based on the upstream project’s master. Jitsi linode.

WARNING: These command will backup master to old_master and then force pushes a brand new master to your GitHub repository.

Project dedicated organization


Projects can also choose to host their repositories in dedicated organization instead of the Eclipse's one. It must be named eclipse-<projectname>

Retrieved from ''