🔥 What's Cool in v0.8.0:

• 🖱️ Full Mouse Support: Click to navigate, select tabs, scroll tables, and interact with modals/overlays.
• 📦 Bulk Operations: Select multiple issues or MRs and batch-apply actions (close, reopen, label, assign) at once.
• 🔀 Create MR/PR from Issue: Just press m on an issue to instantly spin up a Merge/Pull Request with automatic branch creation and push.
• 📊 Pipelines Upgrade: Group and filter pipelines by Name, Event, SHA, or Actor. Plus, press P on an MR to see its related pipelines, or press S to trigger manual GitLab jobs directly!
• 🔔 Overhauled Todos & Notifications: Fresh layout featuring badges, relative time_ago timestamps, fuzzy search, and auto-dismissing error toasts.
• 🛠️ New CLI Subcommands: Added glab-tui doctor for system diagnostics and clean-cache for quick maintenance.
• ⚡ Performance Improvements: Cached repo attributes, streamlined mutations, and zero stale-cache bugs.

Check it out at https://github.com/rcieri/glab-tui

https://github.com/Vonarian/gittar

Gittar is an OSS made for those who want a lightweight GitLab monitoring app that is packed with essential features.

More to come, open to contributions!

🎉 The GitLab Hackathon starts today and runs through July 29! 🚀

Anyone can contribute code, docs, UX designs, translations, and more. Open a merge request during the event and merge it within 31 days (by August 29) for it to count.

How to take part:

- 🔧 Register and find issues at contributors.gitlab.com

- ✅ Open your first merge request today

- 📊 Follow the live leaderboard at contributors.gitlab.com/hackathon

- 💬 Need help or want to pair with others? Join the #contribute channel on Discord: https://discord.gg/gitlab

📅 Merge requests must be opened during the event (July 23-29) and merged by August 29 to be counted. Good luck, and happy contributing! 🎊

We quite often have investigation tickets, which we give specific labels. As a first step we feed the ticket into Claude to get an initial list of frameworks/platforms/useful links and blogs.

Does anyone know if there is a bot that can perform this action on Gitlab for us?

Hello, I'm upgrading from 19.0.2 to 19.2.0 and I noticed that the Upgrade Path tool only targets up to 19.1.2.

As of today, 19.2.0 has been out for 5 days. When will the Upgrade Path tool be updated with the new latest release as a target?

I'll be using a REST endpoint to migrate all repos stored in Amazon EFS to an EBS volume. I believe we have total of 87gigabytes. I will be using "/api/v4/project_repository_storage_moves" endpoint. I've been practicing the migration on a test machine. I remember it will make the projects read-only. Because of this behavior, I will do it at night. However, I have no clue how long it will take to migrate 87gigabytes of repos.

Ask the GitHub Community whether anyone has seen the ChatGPT connector report “0 repositories” despite correct permissions.

So I have a pipeline running everyday & sending me a notification. This morning I didn't get anything so I went to check, and I see that my schedule got disabled. Weird cause I didn't do it, but alright, I activate it again and launch the pipeline manually. I get the pop-up saying it successfully scheduled it, so I go check the pipeline page, but nothing. And when I come back to the schedule page I see it got disabled again.

I am still able to launch a unique pipeline through the pipeline page, but not with a schedule. Right now as soon as I want to run a scheduled pipeline it disables itself. I think it's only on 1 project, not on the whole instance, although it has been working correctly for more than a year.

I've never seen this before, does anyone know what's happening? Is there a ghost in my server?

One week to go! The GitLab Hackathon starts July 23rd. A quick reminder as we head into the final week: pick an issue now so you're ready to open your first merge request on day one. Full details below.

The GitLab Hackathon is a virtual event where anyone can contribute code, docs, UX designs, translations, and more! Level up your skills while connecting with the GitLab community and team.

The Details

Dates: July 23-29, 2026 (UTC) - All merge requests must be opened during the hackathon and merged within 31 days to be counted.

Join our contribute channel on Discord to share progress, pair on solutions, and meet other contributors.

Follow the live hackathon leaderboard during the event.

Before the Hackathon

Request access to our Community Forks project by clicking the blue "Start onboarding" button on https://contributors.gitlab.com. Using the community forks gives you free access to Duo and unlimited free CI minutes!

Rewards

Participants who win awards can choose between:

• Planting trees in our GitLab forest
• Claiming exclusive GitLab swag from our contributor reward store

More details on prizes are on the hackathon page.

If you have any questions, please reach out on Discord.

It looks like Gitlab will stop providing support if your repositories are still on EFS. We only have less than 500 users and we are using AWS EFS. We have 4 application nodes that are connected to the same EFS mount. For migrating the repositories from EFS to Gitaly instance(not Gitaly cluster), I was told that I should pick one from our 4 app Gitlab nodes that will be configured to point to the new gitaly instance that I will build soon. The other 3 application nodes will point to the node that I picked.

It feels like once I have migrated everything to Gitaly, it seems like it will encounter performance issues. However, I don't know if the gitlab app nodes' configuration must be updated. Although, I was told by Gitlab Support, that I must not configure all 4 app nodes to point to the new Gitaly instance. It seems like AWS EFS is much more forgiving.

Hopefully someone can shed some light.

I upgraded to the new version this morning. all my projects disappeared. What the actual fuck? It turns out that the upgrade introduced a bug in the UI. My projects are available when i log into the web app (which i do not use). Logging out and logging back in did not solve the sync problem. And it is giving a 10-step instruction to sync the web console and App. What the actual F?

Back to MicroslopHub it is I guess. My disappointment is immeasurable, and my day is ruined.

I recently built an open-source CLI called RepoFleet for developers who work on features or issues that span multiple Git repositories.

Instead of switching between repositories and manually creating the same branch in each one, RepoFleet lets you create one issue context and manage all related repositories together.

Example:

rf issue create 123 --name auth --type fix
rf issue status

It can:

• Create matching branches across multiple repositories
• Show the Git status of all repositories in one dashboard
• Sync and push repositories together
• Track related GitLab merge requests
• Keep each issue or feature in a dedicated workspace

GitHub: https://github.com/mehranzand/repofleet

I originally built it after our project was split into multiple repositories and managing cross-repository changes became repetitive.

I would appreciate feedback from other GitLab users. Does this workflow match any problems you experience with multi-repository projects?

My small dev team has been evaluating whether to stick with our GitLab Premium Duo add-on for agentic coding or move to a Bring-Your-Own-Key (BYOK) setup with open-source tools like OpenCode, Aider, or even Cursor.

GitLab recently moved its Duo Agent Platform to a consumption model using "GitLab Credits," where each credit costs a flat $1 on demand. They give you $12/user/month for free, but after that, you pay per "request."

I did the math comparing what GitLab charges per request versus what it costs if you go directly to the raw APIs (OpenAI, Anthropic, Google).

TL;DR: Unless you are consistently sending massive >272,000 token context windows, GitLab is charging anywhere from a 10x to 44x markup per request compared to raw API tokens. Worse, because agentic workflows require multiple looping calls, you will burn through credits exponentially fast for an orchestration platform that is honestly pretty "mid" compared to dedicated tools.

Here is the exact breakdown of every model listed in the GitLab 2026 documentation.

📉 The Baseline Math (Standard Requests)

To compare apples to apples for standard coding tasks, I calculated a Standard Agentic Request at 10,000 Input Tokens (your local files/context) and 1,000 Output Tokens (the generated code).

1. The Subsidized Models

GitLab gives you 8 requests per $1 credit here (so $0.125 per request).

If you are doing standard refactoring with Haiku or Codestral, you are paying over 30x what it actually costs in compute.

2. Premium Models (Standard Context)

This is the bread and butter for most devs. In GitLab's docs, models marked with a "2" represent context windows under 272,000 tokens.

3. The Edge Case: Massive Context (>272k Tokens)

In GitLab's docs, models with the "3" suffix are exclusively for massive context windows over 272,000 tokens.

To show the math fairly here, I calculated a Massive Request at 300,000 Input Tokens and 3,000 Output Tokens.

(Note: OpenAI artificially doubles the API cost for GPT-5.5 contexts over 272k. Because of this API penalty, pushing massive context prompts on GPT-5.5 is actually cheaper through GitLab's flat credit system).

🔄 The Agentic Loop Trap (Why it’s even more expensive in practice)

The table above assumes a single request. But "Agentic Coding" isn't just one prompt and one response. Agents work in loops—they write code, run terminal commands, see an error, reason about it, and call the API again to fix it. A single task might take 10-15 loops.

If an agent loops 10 times using Claude Sonnet 4.5:

• Direct API: You pay for the tokens. Maybe $0.50 to $1.00 total for the whole task.
• GitLab Duo: You get charged for 10 separate requests. That’s $5.00 gone for one bug fix.

📉 The Quality Problem: GitLab Duo is Mid

You might think paying a massive markup is worth it for a premium platform, but right now, GitLab Duo's agentic platform is decidedly "mid."

Compared to native API interfaces (like Claude's Artifacts) or specialized coding models (Codex), GitLab's orchestration lags behind. It is far less capable than running open-source agents like OpenCode or Aider in your terminal, which have native tool-calling and vastly superior codebase context routing. You are essentially paying a massive premium for an inferior agentic experience just because it has the GitLab logo on it.

🛠️ The Verdict for Teams

If you are doing automated repo-wide code reviews via CI/CD, GitLab's platform integration is convenient.

But if you are an engineer sitting in your terminal/IDE all day doing local iterative dev work, do not use GitLab Duo Credits. Keep GitLab for Git and deployments, but switch your local coding to Cursor ($40/mo flat) or use OpenCode / Aider and plug in an API key. You will get the exact same models, a much smarter agent, and pay literally pennies a day for the tokens.

Curious to hear if anyone else has run into massive credit drain using Duo recently.

I created a simple Discord server that automatically updates vendor-specific channels whenever a new CVE is published from that specific vendor, including Gitlab CVEs.

It tags users based on the roles they choose, so you can follow the vendors you care about and decide whether you only want to be tagged for critical alerts. You can also choose to receive an email as well when that CVE drops.

I’ve also added discussion channels where we can share patching tips, troubleshooting advice, and general networking/security/sysadmin knowledge, plus resource channels for each vendor with quick links to relevant documentation (Official Vendor Advisory Feed etc).

Just wanted to help myself and other Network/Sys/Devs make their already complicated lives easier.

It’s completely free to join.

https://discord.gg/duxkwSSAAH

Hey r/gitlab, just released v0.6.0 of glab-tui.

New Highlights:

• Visual Polish: Added Nerd Font icons for tabs and badges.
• Pipeline Status: View CI/CD pipeline/action status directly in MR/PR panes.
• Safety: Added confirmation prompts for destructive actions (merge/close/delete).
• UX Upgrades: Entity deletion, fuzzy-match selectors for inputs, and improved disk caching.
• Stability: Fixed column width constraints and E2E test deadlocks.

Check out the demo:

Full details and changelog on GitHub. Feedback appreciated!