This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556

Open
dericksozo wants to merge 1 commit into
base:main
Choose a base branch
from
Open

Docs: GitLab Integration #556

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 2 additions & 1 deletion docs/getting-started/smart-git-sync.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)
96 changes: 96 additions & 0 deletions docs/getting-started/sync-with-gitlab.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.
1 change: 1 addition & 0 deletions sidebars.js
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
items: [
"getting-started/smart-git-sync",
"getting-started/sync-with-github",
"getting-started/sync-with-gitlab",
"getting-started/sync-with-bitbucket",
"getting-started/sync-with-aws-codecommit",
// "getting-started/sync-with-git-differences-between-plans",
Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content

This repository was archived by the owner on Feb 6, 2025. It is now read-only.

Docs: GitLab Integration#556
 Open

dericksozo
wants to merge
1
commit into

base:main
Choose a base branch

from

 Open


Docs: GitLab Integration
#556
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view

Binary file addeddocs/getting-started/assets/sync-with-gitlab/add-gitlab-org.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/authorize-gitlab.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/commit-and-build.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/create-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/merge-request.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file addeddocs/getting-started/assets/sync-with-gitlab/select-gitlab-repo.png

View file


Open in desktop

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

3 changes: 2 additions & 1 deletion
docs/getting-started/smart-git-sync.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -26,7 +26,7 @@ The primary advantage of using Smart Git Sync is its ability to simplify the pro
When you perform a new build on your Amplication project, Smart Git Sync automatically triggers the creation of a commit on the `amplication` branch.

:::note
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and GitLab as git providers.
Amplication supports [GitHub](/sync-with-github), [Bitbucket](/sync-with-bitbucket), [AWS CodeCommit](/sync-with-aws-codecommit), and [GitLab](/sync-with-gitlab) as git providers.
:::

This commit encompasses all the files that were added, removed, or changed since the last build.
Expand DownExpand Up@@ -97,5 +97,6 @@ Smart Git Sync is a powerful feature that simplifies the integration between Amp
Learn how to sync your service with your preferred git provider:

- [Sync With GitHub](/sync-with-github) (Free, Enterprise)
- [Sync With GitLab](/sync-with-gitlab) (Enterprise)
- [Sync With Bitbucket](/sync-with-bitbucket) (Enterprise)
- [Sync With AWS CodeCommit](/sync-with-aws-codecommit) (Enterprise)

96 changes: 96 additions & 0 deletions
docs/getting-started/sync-with-gitlab.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
---
id: sync-with-gitlab
title: Sync with GitLab
sidebar_label: Sync with GitLab
slug: /sync-with-gitlab
toc_max_heading_level: 2
---

# Sync with GitLab

Amplication provides seamless integration with GitLab repositories, enabling automated code synchronization for your services. This integration allows you to maintain full control of your generated code with GitLab's version control features.

## Add GitLab Organization

Follow these steps to add your GitLab organization:

1. Navigate to the [Service Catalog](/service-catalog)
2. Select the **Git Settings** tab
3. Click **Change Repository** if a repository is already connected
4. Open the **Select Git Organization** dropdown
5. Choose **Add Organization**
6. Select GitLab from the provider list

![Add GitLab Org](./assets/sync-with-gitlab/add-gitlab-org.png)

## Authorize GitLab Access

When you select GitLab, you'll be redirected to GitLab's authorization page. Here you'll grant Amplication the necessary permissions to interact with your repositories.

![Authorize GitLab](./assets/sync-with-gitlab/authorize-gitlab.png)

## Configure Repository

After authorization, you'll have two options for repository setup:

### Option 1: Select Existing Repository

Choose from your available GitLab repositories in the repository selection modal.

![Select GitLab Repo](./assets/sync-with-gitlab/select-gitlab-repo.png)

### Option 2: Create New Repository

Click the "Create repository" button to set up a new GitLab repository.

![Create GitLab Repo](./assets/sync-with-gitlab/create-gitlab-repo.png)

## Service-Specific Repository Settings

Amplication provides two levels of Git configuration:

- **Project-level Git Settings**: Located in the Service Catalog's Git Settings tab, this controls the default repository settings for all services in your project
- **Service-level Git Settings**: Found within each individual service's settings, this allows you to override the project-level configuration for specific services when needed

When you override the project settings for a service, that service will maintain its own independent Git configuration separate from the project defaults.

To configure Git settings for a specific service:

1. Access your service from the Service Catalog
2. Navigate to the service's Git Settings page
3. Toggle **Override project settings**
4. Follow the repository setup steps to configure a service-specific repository

## Create Merge Requests

To push your changes to GitLab:

1. Make your desired changes in Amplication
2. Access the pending changes sidebar in your service catalog
3. Click "Generate the code" to initiate the build process

![GitLab Merge Request](./assets/sync-with-gitlab/merge-request.png)

## View Commits and Builds

To track your changes:

1. Go to your Service Catalog
2. Click on the Commits tab
3. View all your builds and their corresponding merge requests

:::important
Do not delete the `amplication` branch. This branch is essential for Amplication's synchronization process.
:::

![Create GitLab Repo](./assets/sync-with-gitlab/commit-and-build.png)

## Next Steps

Learn more about Amplication's Git integration features:

- Branch management strategies
- Merge request workflows
- Conflict resolution

Visit our [Smart Git Sync](/smart-git-sync) documentation for detailed information.

1 change: 1 addition & 0 deletions
sidebars.js

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -77,6 +77,7 @@ const sidebars = {
 items: [
 "getting-started/smart-git-sync",
 "getting-started/sync-with-github",
 "getting-started/sync-with-gitlab",
 "getting-started/sync-with-bitbucket",
 "getting-started/sync-with-aws-codecommit",
 // "getting-started/sync-with-git-differences-between-plans",
Expand Down