Developing against interacting components or features

It’s not uncommon that a single code change can reflect and interact with multiple parts of GitLab codebase. Furthermore, an existing feature might have an underlying integration or behavior that might go unnoticed even by reviewers and maintainers.

The goal of this section is to briefly list interacting pieces to think about when making backend changes that might involve multiple features or components.

Uploads

GitLab supports uploads to object storage. That means every feature and change that affects uploads should also be tested against object storage, which is not enabled by default in GDK.

When working on a related feature, make sure to enable and test it against MinIO.

Merge requests

Forks

GitLab supports a great amount of features for merge requests. One of them is the ability to create merge requests from and to forks, which should also be highly considered and tested upon development phase.

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support