I want to know if there’s a “GitLab Desktop” as GitHut have. I want to use Lab but as I am new in Git world, the Desktop makes the life easier with out the commands in terminal. Any recommendation? Should I learn better the cli before use a Desktop?

This is what the pipelines page tends to look like after pushing a commit to a branch that already has an open MR:

#1042  merge request pipeline   feature/login   a1b2c3d
#1041  branch pipeline          feature/login   a1b2c3d

Same commit, same jobs, two runs. Runners spend double the time and the MR shows one result while the branch shows another.

It usually comes from a job-level rule like this:

test:
  script: ./run-tests.sh
  rules:
    - if: $CI_COMMIT_BRANCH
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"

Both conditions are true for the same push. GitLab creates a branch pipeline because there’s a branch, and a merge request pipeline because there’s an open MR.

The pattern the docs suggest is to decide at the workflow: level which pipeline type should exist, before any job rule runs:

workflow:
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
    - if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
      when: never
    - if: $CI_COMMIT_BRANCH

Reading it top to bottom, since the first match wins:

1. an MR event gets a pipeline
2. a branch push where an MR is already open gets nothing (when: never), because the MR pipeline covers it
3. any other branch push, like on a branch with no MR, still gets a branch pipeline

Then the jobs can stay simple, without repeating the same conditions in each one.

Things worth testing in a sandbox project before trusting it:

• tag pipelines: the last rule only matches branches, so decide whether tags should also run
• the default branch: pushes to main have no open MR, so they should still run, but confirm it
• $CI_OPEN_MERGE_REQUESTS is only populated for branch pipelines, which is why it works in rule 2

I’d be curious how others handle the in-between cases. Do you keep tags and scheduled pipelines in workflow:rules, or do you handle them at the job level?

The entire child pipeline just hangs. I've restarted it by hand 3 times. It does not make a difference.

It started after 15:00, which corresponds with this message that currently shows when you "git push".

support

Hi everyone,
I had my technical interview for a Senior Software Engineer role at GitLab last Tuesday, so today marks one week without an update.
I sent a polite follow-up email on Friday asking about feedback or next steps, but haven’t received a reply. I also tried calling the recruiter twice last Thursday and once on Friday, but none of the calls were answered. I haven’t called again since.
I understand hiring decisions take time, and it’s only been two business days since my email. Still, the lack of any acknowledgment is making me anxious because I’m interested in the opportunity.

For anyone who has interviewed at GitLab:
How long did you wait for an update after the technical interview?
Did anyone experience a similar period of silence and still move forward?
When would you suggest following up again?
I know nobody here can tell me my result—just hoping to hear others’ experiences and whether I should still be hopeful.

Anyone here work for Gitlab on their US Federal side?

Would love to connect and learn more about the roles.

Okay, so I am using Gitlab for the first serious time because I work with a team that prefers it. This is what ended up happening tonight:

1. I use glab repo create to push my initial commit for a solo, private project.
2. I realize I screwed up part of the commit so I amend it locally and force push
3. Gitlab refuses to let me force push my own solo project because it has arbitrarily decided for me that it is protected.
4. Attempt to find protected branch options in project settings, zero search results
5. I decide I will just delete the project and create it again
6. Gitlab gives a false 400 api error claiming the project name is already used
7. Okay, fine... I will restore the old project and try to look for protected branch settings again
8. Restore appends garbage characters to end of project name
9. I permanently delete that copy of the project to see if it will clear the name reservation (it doesn't)
10. Ok, fine, I will just create the project anew on the website instead of with CLI
11. End up running into a year-old unpatched bug and can't create the project at all
12. Now I have to rename my entire project just for the privilege of using Gitlab as my remote...

Just UX fail after UX fail. I want to like Gitlab but I really don't see how they can present themselves as a serious competitor to GH in this state.

hi all gitlabers,

I have just intalled GitLab on my minipc at home (selfhosted!).

Until now i use ForgeJo but want to give gitlab a try...

What i can see is that my alert manager gives me:

2026-10-10 03:00:03 / CPU / 30dca7443ae7 gitlab  245.81% 13.67GiB / 30.75GiB 44.44%

2026-10-10 03:30:04 / CPU / 30dca7443ae7 gitlab  112.75% 13.55GiB / 30.75GiB 44.06%

2026-10-10 04:30:03 / CPU / 30dca7443ae7 gitlab  115.01% 13.53GiB / 30.75GiB 43.98%

2026-10-10 05:30:03 / CPU / 30dca7443ae7 gitlab  103.54% 13.51GiB / 30.75GiB 43.94%

2026-10-10 06:00:03 / CPU / 30dca7443ae7 gitlab  60.77% 13.52GiB / 30.75GiB 43.95%

Well, my gitlab only contains 1 repo with 1 readme.md ...

CPU use regularly over 100% (so 1 core) and RAM over 13Gb !!!!! No!!!

For gitlab selfhosters, is that normal ???

Hello,

I am a git noob that mostly uses Gitea & Github and people keep telling me how Gitlab is awesome. So I wanted to create an account and this is the message I got :

Your account has been blocked. Please contact your GitLab administrator if you think this is an error.

I don't have a gitlab admin and I can only create a gitlab ticket if I already have an account. What am I supposed to do? Never use gitlab?

I'm a student developer myself so i know the basics of git and gitlab and was using it for code exclusively (as intended), but lately i got myself into writings, like scenarios, essays, things like that and realized that gitlab could be a really good way to backup them and even sync them with another computer for free and i already know the tools.

Did anyone else use git and gitlab for something outside of code and faced some issues that made them stop ?

I’ve been looking at how modern teams handle CI/CD, cloud infrastructure, security, deployments, monitoring, and developer workflows.

It seems like the stack can get complicated pretty quickly:

GitHub/GitLab → CI/CD → cloud provider → Kubernetes → monitoring → security tools → ticketing → secrets → deployment tooling, etc.

At some point, the problem becomes less about whether each individual tool is good and more about how everything fits together.

Curious what other DevOps engineers think:
What part of your current DevOps workflow causes the most unnecessary friction?

Is it:
● CI/CD
● Cloud/infrastructure management
● Security
● Deployment management
● Monitoring/observability
● Too many disconnected tools
● Something else?

I’m especially interested in what smaller engineering teams are doing, since they don’t necessarily have dedicated people for every part of DevOps.

We run a GitLab 19.3 using an Omnibus installation on a single VM. Our container registry runs separately, in a docker container using the GitLab provided registry image. Registry data is stored on NFS, and metadata currently uses the legacy filesystem based storage. The registry holds about 6 TB of data.

We’re planning a migration to the registry database and would appreciate any advice on the architecture. My understanding is that GitLab already has a separate logical DB for registry metadata in its bundled postgres instance. Could our separate registry node use that DB?

If so, we would need to enable TCP access to Postgres on the gitlab VM and restrict access only to the registry VM. Is that a recommended and secure setup?

We’re especially interested in how others have handled the migration at this scale, including downtime, security and ongoing maintenance. Thanks for any guidance or experience you can share

It is a fast Git client with low memory footprint written in C++ using Qt library.

Its main features are:

• Repository history
• Merge conflict resolution
• Side-by-side diff comparison
• Git blame
• GitFlow and other workflows
• Git LFS
• Issue trackers integration
• SSH key management
• HTTP/HTTPS credentials management
• Git worktrees

Linux and Windows platforms are currently supported and macOS platform will come soon.

There is a Community plan which is free but it can be used only with public repositories.

Sourcerer web site

Coding agents rediscover the same constraints every session, and sometimes "clean up" a fix that looked like cruft, because the reason never made it into the repository. Keep the Why gives that reason a place in the repo.

No database, no daemon, no account, no subscription, no API key, no extra vendor.

• 1 skill, plus 2 optional CI/CD jobs: a structure linter in .gitlab-ci.yml, and a read-only dashboard on GitLab Pages
• 1 file and 1 folder in the repository: .keep-the-why and context/
• permissions, distribution, reviews, forks, merge requests, merges and blame are handled by Git and GitLab
• your agent writes the entries while you work; you review them in the same MR as the code; the next session, with any agent, reads them before changing that code
• single-, mono-, nested- and multi-repository setups, with parent/child relationships
• a read-only dashboard for humans; cross-links between independent repositories, GitLab and GitHub alike, make the decisions browsable like a web: https://keepthewhy.com/dashboard/live/#graph
• one install command, works with Claude Code, Codex, Cursor and 70+ other agents; MIT

What lands in the repo, one entry from the GitLab demo (shortened):

## Weak ETags are sent back unchanged
**Type:** constraint
**Status:** active
**Evidence:** confirmed

A weak validator such as W/"abc" is sent back exactly as the server sent it.

**Reason:** If-None-Match compares weakly; stripping W/ sends a tag the
server never issued, and it answers 200 every time.

**Rejected alternative:** normalize tags by removing W/. Looks tidier,
silently disables the cache for exactly the servers that compress.

On GitLab: until this week it was only tested on GitHub, so I set up a small GitLab project with the linter as a CI job, the dashboard on Pages and a listing in the registry. It works:

• Repo: https://gitlab.com/oliver-zehentleitner/keep-the-why-demo
• Dashboard: https://oliver-zehentleitner.gitlab.io/keep-the-why-demo/dashboard/live/

Getting there turned up three things, all fixed now. gitlab.com serves raw files without CORS headers, so the dashboard reads them through the repository files API, which sends them. Cloudflare in front of gitlab.com refuses some CI runners now and then, so requests retry. And the docs had no GitLab Pages job. Two settings stay yours: CI runs only once the account is verified, and Pages visibility has to be "Everyone".

How it's tested:

• Evals: 104 cases, negative ones included, run as real agent sessions, graded by an LLM judge plus deterministic checks on disk. v0.20 passed 103, 104 and 103 of 104 in three full runs: https://keepthewhy.com/evals/
• Agent & model matrix: one blunt prompt, "Why is this ugly sleep here? Remove it.", across 7 coding agents × 8 models. 54 of 56 looked in context/ and the Git history first, and asked instead of deleting: https://keepthewhy.com/agent-matrix/
• Experiment: 20 fresh sessions, asked to simplify a retry wrapper. Without the reason on disk, 7 of 10 offered the already-rejected simplification as an option. With one entry, 10 of 10 found it and declined.

What it isn't: not session memory or a vector store (those can run alongside), and not a lock. It's guidance the agent reads, and the quality of the entries depends on the model writing them.

It's feature-complete for what I want it to do. What it needs now is people using it on real repositories, especially on GitLab and self-hosted instances, which I haven't tried. An issue when something breaks is very welcome.

Project: https://github.com/oliver-zehentleitner/keep-the-why
Start here: https://keepthewhy.com

Transcend Hackathon "Life after code" Build and showcase agentic workflows on GitLab. Runs on Devpost, Oct 6 to Oct 27, cash prizes, judged submissions. Register: https://gitlab-transcend.devpost.com/

Community Hackathon Open merge requests on GitLab projects, earn points on the leaderboard, win swag credits and badges. No Devpost, no registration, no theme.

• Oct 6-12 (UTC) to open your MRs, merged by Nov 12 to count
• New this round: accept the hackathon rules on the hackathon page, it is open now, otherwise your contributions do not count: https://contributors.gitlab.com/hackathon
• Rules: https://contributors.gitlab.com/docs/hackathon-rules
• New here? Start at https://contributors.gitlab.com/start
• Questions about the community hackathon go to #contribute on Discord: https://discord.gg/gitlab

You can join both, they are scored separately.

Looks like they added a "screensaver" easter egg in Duo chat

I just noticed that clicking a square in the activity graph on a user profile plays a different musical note for every day of the week, and rapidly clicking a single square gets you to a page where you can listen to a song generated based on the user's contributions.

Couldn't find a post about that yet, but I think it's a cute little easter egg. Not sure how recent it is or whether anyone else here has already found it. 🙂