Adjusting to GitHub Migration

1

All public repositories from our Bitbucket server have been migrated to [[GitHub>>url:https://github.com/kieler||shape="rect"]].

2

If you want to continue to use your already cloned repositories or you are currently using an Eclipse installation for Kieler created with Oomph, you should to take action according to the following guides.

3

4

Private repositories are now located in the [[IfI GitLab>>url:https://git.informatik.uni-kiel.de||shape="rect"]]. There is a separate** **[[internal migration guide>>url:https://git.informatik.uni-kiel.de/ag-rtsys/admin/bitbucket-migration/-/wikis/Migration-Guide||shape="rect"]] for members of our group.

5

6

= Updating Remote URL =

7

8

If you have unpushed branches/commits or you want to continue to use your a repository that was initially cloned from our Birbucket system, you have to adjust the remote URL.

9

10

1. Open a terminal

11

1. Change the current working directory to your local repository

12

1. (((

13

List your existing remotes in order to get the name of the remote you want to change (usually //origin//)

$ git remote -v

> origin ssh://git@git.rtsys.informatik.uni-kiel.de:7999/KIELER/<repo>.git (fetch)

18

> origin ssh://git@git.rtsys.informatik.uni-kiel.de:7999/KIELER/<repo>.git (push)

The given example uses an URL for access via SSH, if you are using HTTPS, the URL might differ.

23

24

)))

25

1. Find the new repository location on [[GitHub>>url:https://github.com/kieler||shape="rect"]] (or [[IfI GitLab>>url:https://git.informatik.uni-kiel.de||shape="rect"]] for internal ones)

26

1. Click on clone to inspect the new URL of the repository

27

1. (((

28

Change your remote's URL to the new location using the {{code language="none"}}git remote set-url{{/code}} command.

29

30

31

$ git remote set-url origin git@github.com:kieler/<repo>.git

)))

1. (((

(optinal) Verify that the remote URL has changed.

$ git remote -v

> origin git@github.com:kieler/<repo>.git (fetch)

40

> origin git@github.com:kieler/<repo>.git (push)

)))

= Oomph Setup =

With the migration to GitHub the Oomph setup configurations for the Kieler projects changed. It is necessary to create a fresh installation of your developer Eclipse with the new Oomph setup files in order to get a correct configuration.

47

48

If you already installed an developer Eclipse for Kieler following [[this guide>>doc:KIELER.TO DELETE.Getting Eclipse.WebHome]], you need to perform these steps.

49

50

1. (optional) If you follow the guide above, you can make sure that you can push all of your outstanding commits before discarding you current developer Eclipse installation.

51

1. Start the Eclipse installer

52

1. Select any product (e.g. Eclipse Product) and click next.

53

1. Select the KIELER folder in the <User> directory and then click the red X in the tool bar.

54

[[image:attach:delete_old_setup.png]]

55

1. Now the old configuration is removed and you can close the installer

56

1. Next follow the new instructions for the Oomph setup that are located in the wiki of the corresponding repository.