search

pingidentity / ssam

Self-Service Account Manager
Apache License 2.0
7 stars 2 forks source link

Migrate this repository to Ping's internal GitLab environment #1

Open dirmgr opened 7 years ago

dirmgr commented 7 years ago

As per Ping policy, public UnboundID projects on GitHub should be migrated to the Ping Identity organization on GitHub, and private projects should be migrated to Ping's internal GitLab environment. This private repository will be migrated to GitLab, but that migration has not yet been scheduled. See https://docs.google.com/a/pingidentity.com/document/d/1bOyHc38PmV0ZdLu7BKcnzgnz60mC2B1fYUq2U40BcoM/edit?usp=sharing for more information.

dirmgr commented 7 years ago

We'd like to get off the UnboundID GitHub organization as quickly as possible, so I plan to migrate this repository to Ping's GitHub organization tonight. We may migrate it to GitLab at some point in the future, but migrating to Ping's GitHub organization will reduce the urgency.

dirmgr commented 7 years ago

This repository has been migrated from the UnboundID organization to the Ping Identity organization on GitHub.

Previous URL: https://github.com/UnboundID/ssam Previous Clone URL: git@github.com:UnboundID/ssam.git New URL: https://github.com/pingidentity/ssam New Clone URL: git@github.com:pingidentity/ssam.git

selliott512 commented 7 years ago

A possibly dumb question about this migration since I'm getting these notices - does the migration preserve the history along with having the same SHA-1 hashes? I'm not familiar with GitLab, but if it's like GitHub it should be possible to do that by simply pushing into the new empty repository from on old checkout.

On Wed, Apr 12, 2017 at 2:26 AM, Neil Wilson notifications@github.com wrote:

This repository has been migrated from the UnboundID organization to the Ping Identity organization on GitHub.

Previous URL: https://github.com/UnboundID/ssam Previous Clone URL: git@github.com:UnboundID/ssam.git New URL: https://github.com/pingidentity/ssam New Clone URL: git@github.com:pingidentity/ssam.git

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pingidentity/ssam/issues/1#issuecomment-293496317, or mute the thread https://github.com/notifications/unsubscribe-auth/ACRRkp0bMZoYQ55H0OHot5dqsmyND9t9ks5rvHyigaJpZM4MQOPC .

--

| Steven Elliott | http://selliott.org | selliott512@gmail.com |

dirmgr commented 7 years ago

The migration from one GitHub organization to another should preserve pretty much everything. All of the commit history should be identical, and all of the issues, releases, wiki content, forks, etc. should be left intact. The URLs do change during the process, but GitHub even provides redirects that ensure that clients using the old URLs are automatically sent to the right place. So you should be able to continue using the project as you had been with no interruption, although if you have a clone of the repository, it might not be a bad idea to update that clone to point to the new location. You can do that with a command like:

git remote set-url origin new_url git@github.com:pingidentity/ssam.git

See https://help.github.com/articles/about-repository-transfers/ for more information about transferring GitHub projects between organizations.

If we do end up migrating some of these repositories from GitHub to GitLab, the transition won't be as seamless, but it does look like GitLab provides utilities to do most of the heavy lifting for you. But in this case, we had a pretty urgent need to get our repositories out of the UnboundID organization, so migrating them to the Ping Identity organization was the fastest way to do that.

If you're asking specifically about the ssam repository and why you're not seeing anything in it, that's because there isn't any content in it. I have no idea whether there's any intention to put anything in it or not, but I went ahead and migrated it anyway just in case there was a legitimate need for it.