Migrate platform/eclipse.platform.ui to GitHub https://github.com/eclipse-platform/eclipse.platform.ui

added Migration ~16280 labels

assigned to @fgurr

Import is in progress...

First attempt failed. Retrying...

It seems mostly working now. However, the default branch is R1_0. Can you please make the repo use master as default?

Unless I confirm that the import is done, please assume that it is not done yet. Your patience is appreciated.

Third try (which often works), otherwise I'll do a manual import.

Failed as well. I will import the repo manually tomorrow.

@fgurr : R1_0 is still default branch in https://github.com/eclipse-platform/eclipse.platform.ui. Could you please change to master?

This is a symptom of an incomplete import. Please also see:

Unless I confirm that the import is done, please assume that it is not done yet. Your patience is appreciated.

@mistria : bug description is wrong.

Please migrate platform/eclipse.platform.ui to https://github.com/eclipse-platform/eclipse.platform.ui.tools

eclipse.platform.ui should not be migrated to eclipse.platform.ui.tools repo, which is already migrated.

Did you mean to open another ticket to migrate https://git.eclipse.org/r/e4/org.eclipse.e4.tools?

changed the description

bug description is wrong.

Thanks for the note, fixed. Fortunately, @fgurr got it right despite the incorrect description.

@fgurr : I've asked because I saw already two new commits on master being merged that aren't on old repo?

In order to do a manual import I had to reset the repo. So those commits will need to be committed again.

For future imports I will make sure that permissions will only be set after a successful import to avoid such situations caused by impatience.

The manual import succeeded.
Committers will gain access once the sync script runs (~2h).
GitHub actions have been enabled.
Default branch protection for master and R*maintenance branches has been enabled.
Default branch was set to master.

closed

In order to do a manual import I had to reset the repo. So those commits will need to be committed again.

I have them locally, I'll commit them again.

I now got access to the repo. It looks like I have full admin power, more than usual. Is it OK? Also the ECA check didn't kick in.

My bad, it was my fork (which is not referencing the upstream repo anymore since it was recreated)

Designs