Configure CODEOWNERS for repository #89

New Issue

2026-04-11T15:03:10+02:00

lars.winzer commented

2026-04-11 15:03:10 +02:00

(Migrated from git.scicore.unibas.ch)

Task

Summary

GitLab offers the Code Owners functionality "[...] to define who has expertise for specific parts of your project’s codebase."

When modifying others people code, the merge request will not be able to be merged, until all involved owners gave thier ok.

This has become a necessity due to "incidents" in the present, past and to enforce guidelines.

Context

GitLab and QC

Current Progress

Evaluate if this instance has at least the required "Premium" tier to use this feature
Assign one or multiple codeowners to each area
Create CODEOWNERS file in ./.gitlab/CODEOWNERS
Activate "Require Code Owner approval" for protected main branch

Notes

See GitLabs own documentation on this regard: https://docs.gitlab.com/user/project/codeowners

Checklist

I outlined checkpoints describing phases of my work related to this task
I added relevant labels
I linked to other issues or branches that must be completed first

## Task  ### Summary GitLab offers the [Code Owners](https://docs.gitlab.com/user/project/codeowners/) functionality "\[...\] to define who has expertise for specific parts of your project’s codebase." When modifying others people code, the merge request will not be able to be merged, until all involved owners gave thier ok. This has become a necessity due to "incidents" in the present, past and to enforce guidelines. ### Context GitLab and QC ### Current Progress - [ ] Evaluate if this instance has at least the required "Premium" tier to use this feature - [ ] Assign one or multiple codeowners to each area - [ ] Create `CODEOWNERS` file in `./.gitlab/CODEOWNERS` - [ ] Activate "Require Code Owner approval" for protected main branch ### Notes See GitLabs own documentation on this regard: [https://docs.gitlab.com/user/project/codeowners](https://docs.gitlab.com/user/project/codeowners/#codeowners-file) ### Checklist - [x] I outlined checkpoints describing phases of my work related to this task - [x] I added relevant labels - [x] I linked to other issues or branches that must be completed first

lars.winzer commented

2026-04-11 15:03:10 +02:00

(Migrated from git.scicore.unibas.ch)

changed start date to April 06, 2026

lars.winzer commented

2026-04-11 15:03:10 +02:00

(Migrated from git.scicore.unibas.ch)

assigned to @lars.winzer

lars.winzer commented

2026-04-11 15:25:09 +02:00

(Migrated from git.scicore.unibas.ch)

changed start date to April 13, 2026

lars.winzer commented

2026-04-14 18:35:59 +02:00

(Migrated from git.scicore.unibas.ch)

I looked into what tier this instance of GitLab could possibly have:

First thing I tried was to find out if this is an enterprise instance. According to this source, there is an API endpoint. The response of this endpoint is as follows, clearly indicating that this instance is NOT enterprise.

{
    "version":"18.10.3",
    "revision":"78b4b5987e9",
    "kas":{
        "enabled":true,
        "externalUrl":"wss://git.scicore.unibas.ch/-/kubernetes-agent/",
        "externalK8sProxyUrl":"https://git.scicore.unibas.ch/-/kubernetes-agent/k8s-proxy/",
        "version":"18.10.3"
    },
    "enterprise":false
}

As there is no indication of the tier (Free, Premium, Ultimate) of this instance, the only practical solution I could think of was to cross-reference the features we can use with the required tier according to the official documentation.

One feature we are already making use of is the Code Quality Report. The feature itself is Free, but the in-line report and pipeline details view are not. Both of which we cannot use.

Therefore, I highly suspect that this instance has only the Free tier, meaning we cannot use the Code Owners feature as it requires at least the Premium tier.

Our next appointment is tomorrow, Wednesday. Then, I will ask about the tier.

I looked into what tier this instance of GitLab could possibly have: First thing I tried was to find out if this is an enterprise instance. According to [this](https://forum.gitlab.com/t/how-to-know-my-enterprise-edition/33752/6) source, there is an API endpoint. The response of this endpoint is as follows, clearly indicating that this instance is NOT enterprise. ```json { "version":"18.10.3", "revision":"78b4b5987e9", "kas":{ "enabled":true, "externalUrl":"wss://git.scicore.unibas.ch/-/kubernetes-agent/", "externalK8sProxyUrl":"https://git.scicore.unibas.ch/-/kubernetes-agent/k8s-proxy/", "version":"18.10.3" }, "enterprise":false } ``` As there is no indication of the tier (Free, Premium, Ultimate) of this instance, the only practical solution I could think of was to cross-reference the features we can use with the required tier according to the official documentation. One feature we are already making use of is the [Code Quality Report](https://docs.gitlab.com/ci/testing/code_quality). The feature itself is Free, but the [in-line report](https://docs.gitlab.com/ci/testing/code_quality/#merge-request-changes-view) and [pipeline details view](https://docs.gitlab.com/ci/testing/code_quality/#pipeline-details-view) are not. Both of which we cannot use. --- Therefore, I highly suspect that this instance has **only the Free tier**, meaning we cannot use the Code Owners feature as it requires at least the Premium tier. Our next appointment is tomorrow, Wednesday. Then, I will ask about the tier.

lars.winzer (Migrated from git.scicore.unibas.ch) closed this issue

2026-04-15 16:17:15 +02:00

lars.winzer commented

2026-04-15 16:17:16 +02:00

(Migrated from git.scicore.unibas.ch)

Closing, as this instance is running on the Free tier.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: University-of-Basel-Studentprojects/Programmierprojekt#89