Skip to content

PORT-15403 Added migration guide to gitlab #2526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

oiadebayo
Copy link
Contributor

Description

Added guide for migrating from gitlab to gitlab-v2

Added docs pages

Please also include the path for the added docs

  • Migration Guide to Gitlab-v2 (build-your-software-catalog/sync-data-to-catalog/git/gitlab/Migration)

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2526.d2ngvl90zqbob8.amplifyapp.com

- **Enhanced performance**: Faster resync with improved API efficiency
- **New capabilities**: Support for pipeline jobs and enhanced group handling

## What's changing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like a general header for changes, but many changes in the doc are not under it.
the sections that describe changes should be under this one, for example "## Blueprint mapping changes" should be "### Blueprint mapping"

Copy link
Contributor

@shariff-6 shariff-6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome 👌
One minor comment on repo paths in files and folders. We use the full repo namespace.
LGTM

@hadar-co hadar-co merged commit 38ef66b into main Jul 10, 2025
2 checks passed
@hadar-co hadar-co deleted the PORT-15403-write-migration-docs-for-gitlab-v-2-in-ocean-docs branch July 10, 2025 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants