Gitlab to GitHub Migration

[ganga201]

Body

We have a script runs on hourly basis to integrate Gitlab with serviceNow and LDAP, this helps us to manage Gitlab groups and permissions. Also integrated with OKTA for SSO.

ServiceNow Group Synchronization: A script or integration likely manages bi-directional synchronization between ServiceNow groups and GitLab groups. When a new ServiceNow group is created (or deleted), a corresponding GitLab group is created (or deleted) as well with the same name.

AD Group User Population: The script extracts users from the Active Directory (AD) group associated with a ServiceNow group. It then assigns user permissions within the GitLab group: The owner of the ServiceNow group becomes the owner of the GitLab group. Other members of the AD group become developers in the GitLab group.

For instance when the script run it will identify the new serviceNow group call S1 and create the Gitlab group with same name S1, also script identify the AD group attached to the S1 and call the LDAP to list out the users and owners. Now script will add these users as developers and AD group owner as Gitlab group owner to S1 Gitlab group

Can this be possible in GitHub cloud platform?

Based on my understanding, GitHub Cloud doesn't have a concept directly equivalent to GitLab groups. Seems I need to integrate GitHub with serviceNow to create all serviceNow groups as orgnizations. Then, for each organization, I use ServiceNow data to retrieve the associated AD group details and add those users as teams within the corresponding GitHub Cloud organization.

Unsure if the above mentioned process works. Any pointers can help us with the migration

[michaelsainz]

Hi @ganga201 - this is a good question!

You're right that GitLab Groups doesn't "exactly" have a similar model when compared to GitHub. A GitHub Team is probably the closest equivalent which sounds like what you want to use. You can use teams to group users together and grant access control rights to repos. You can find out more here.

What the docs don't really emphasize though is that you can also get a list of repos of which the GitHub Team has been granted access to which then can be leveraged for essentially the same thing. When you view a GitHub Team you're given a list at the top of which once of the options is Repositories -

You can also access that list programatically via the API - you can read about that here.

You want avoid creating many GitHub Organizations - we recommend a best practice to try and keep it as small as possible (ideally just a single Org if you can). When you create organizations you also create silos which prevent cross-collaboration and restrict access on a broad scale. By using only a single organization coupled with the use of GitHub Teams though you should be able to keep the best of both worlds - strong access control while still keeping admin/management simple.

Also, you can sync AD/AzureAD/EntraID groups with GitHub Teams using SCIM - link