r/gitlab

I use ai agents as helper I talk to, not for blind vibecoding. One thing I kept noticing is asking agent to write or refactor gitlab ci pipeline, and results are often questionable. It creates a god yaml, outdated keywords, no thought about debugging or developer experience.

I looked for existing skills but did not find anything I would actually trust, most looked generated in one shot. So I spent some time and made my own. Used agent help of course, but went through everything myself and checked it against official docs for GitLab 18+

It covers pipeline structure and refactoring, bash in ci jobs, pipelines and other common patterns, debugging failed pipelines, readable logs and naming

https://github.com/beeyev/skills/

Works with claude code and anything supporting skills format
I have been using it privately for couple of month and improving constantly, maybe it will useful for someone else too

Hey everyone,

I’m dropping a quick update for glab-tui, the TUI I shared previously for managing GitLab (and GitHub) workflows directly from your terminal.

I’ve just released v0.4.0, which includes a number of stability improvements and refinements to make your terminal-based code review and pipeline management even smoother.

If you’re still context-switching between your terminal and the browser for MRs, issues, or CI/CD, give the latest version a look:

https://github.com/rcieri/glab-tui

Thanks to everyone who has checked it out or contributed so far! Would love to hear what you think if you’ve had a chance to test the latest build.

So basically I'm trying to copy a gitlab repository that isn't mine (but I gave guest access) to my github desktop.

When I put it there and input my username with password (I've even tried many different PAT's) it gives me this error message.

If it helps anyone the repository is a Hoi4 mod.

I'm pretty sure my project has merge requests that are still referencing branches, commits and files/assets that don't exist anymore.

I'm pretty certain that these merge requests are causing these files to still be remembered by Git LFS, which costs a lot of storage space

I want to delete all of my closed merge requests, but I can't find a delete button anywhere. Are merge requests (once completed) not supposed to be deleted? or am I blind AF ...

This project has been completely cleaned to only contain 1 branch with 1 super squashed commit, which only references 15.6 GB worth of Git LFS assets.

However, the usage breakdown reports 19.4 GB worth of storage being used for the assets. The remaining 3.8 GB appears to be from old LFS assets that existed before the cleanup, but are no longer referenced by any branch or commit.

Does Git LFS/GitLab have a way to force garbage collection of unreferenced LFS objects?

I recently joined a new company and coming from GitHub and the 100s of integrations for it, the GitLab and especially the GitLab Self Hosted marketplace felt dire.

I was very used to my PRs (and now MRs) landing in a Slack channel like #fe-reviews, and the comments & reviews on it to land in that Slack thread. It meant I never missed comments and my PR/MRs were reviewed MUCH quicker.

Other than Axolo, no other tool that does what I'd like supports GitLab, so I built mergeme.dev

Some of the key features that I wanted myself (and I'm sure others will appreciate) are:

• One Slack message per MR that updates in place (open > in review > approved > merged)
• Review comments as thread replies on that card
• Per-project channel routing - each project can map to whichever Slack channel you want
• GitLab @ mentions ACTUALLY ping the right person on Slack with a one-time username map
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance
• [New] You can set up label mapping too, an MR with "bug" as it's label goes to #qa-reviews instead

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your workflow!

----

Aside from this, I am genuinely curious as to how people handle this problem in their own setup?

My personal story before MergeMe was that I set up webhooks into Slack from GitLab directly and I made a custom webhook triggered workflow to send myself messages when my own MRs were responded to. It was a MESS to look at and it's what unironically pushed me to build a better tool lmao.

Hello, World

I was facing a issue when i used to push commits and i have multiple github accounts to solve that problem i have released gtp

please let me know if you find it useful

https://github.com/sarangkkl/gtp

leave a start on repo if you find it helpful thanks

I'm building Orbit Navigator for the GitLab Transcend Hackathon. It's a Duo skill that uses GitLab Orbit's knowledge graph to trace any SDLC event back to the merge request behind it — and it can open a draft fix.

What it does (one graph query each):

• Which MR shipped what's currently in production?
• Why did the pipeline fail, and which job?
• What breaks if I change this shared library? (blast radius)
• Who resolved these vulnerabilities?
• /guardian --remediate — finds vulnerable dependencies and opens a draft MR that bumps them to fixed versions.

It's just a skill file (no backend, no vector DB) that runs through the Duo CLI with the Orbit MCP connected. The agent calls query_graph on the live knowledge graph directly.

👉 Try the agent directly (AI Catalog): https://gitlab.com/explore/ai-catalog/agents/1011766/

Source code + how to run it from the CLI: https://gitlab.com/gitlab-ai-hackathon/transcend/12108860

Honest heads-up: it's built on the Orbit beta, so there are real rough edges. For example, security Finding nodes get purged in the current beta, so some security traces pivot to durable Vulnerability nodes instead. Custom agents also don't get Orbit by default — you connect it via the Orbit MCP.

What I'd love: if you try it, please break it and tell me. Bug reports, rough edges, queries that return wrong or empty results — all welcome. Easiest way is an issue on the project linked above, or just drop a comment here.

Thanks!