Skip to content

Commit b0c3661

Browse files
committed
Update title
1 parent 8a75097 commit b0c3661

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2024-08-25-migrating-python-packages-from-gitlab-registry-to-gcloud-artifacts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: How We Migrated Our Internal Python Packages From GitLab to Gcloud Artifacts
2+
title: Migrating Internal Python Packages From GitLab to Gcloud Artifacts
33
description: This blog shares the journey of our migration from GitLab registry to Google Cloud Artifacts
44
author: hemantapkh
55
date: 2024-08-25 15:48:00 +0000
@@ -13,7 +13,7 @@ image:
1313
---
1414

1515

16-
At [Docsumo](https://docsumo.com), we recently transitioned our version control system from GitLab to GitHub. One challenge that emerged during this migration was the lack of native support for [Python packages in GitHub](https://github.com/orgs/community/discussions/8542). To address this, we opted to move our internal packages to Google Cloud Artifacts.
16+
At [Docsumo](https://docsumo.com), we recently transitioned our version control system from GitLab to GitHub. One challenge that emerged during this migration was the lack of native support for [Python packages in GitHub](https://github.com/orgs/community/discussions/8542). To address this, and given our infrastructure's alignment with Google Cloud, we transitioned our packages to Google Cloud Artifacts.
1717

1818
Here are the detailed steps I followed to successfully migrate around 250 versions of internal packages from GitLab python registry to Google Cloud Artifacts.
1919

0 commit comments

Comments
 (0)