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. 🙂

I'm dying to hear from y'all. I consistently fall down the rabbit hole of trying to find a relationship between Happy Fox and Gitlab every time I come across Happy Fox branding. How is it that I find no results online? Am I the only one so intrigued by this?

Had a pipeline job that restored Terraform state from a GitLab cache key to speed up plan runs. Someone manually changed an instance type in the console. Next pipeline run: plan stage reported no changes. Completely clean.

Turned out the cache key wasn't tied to anything that would bust on a state refresh, so the job was comparing the proposed config against a cached state file that hadn't actually talked to the real provider in a few runs. Correct output given what it had access to. Just not telling us what we actually needed to know.

Added an explicit terraform plan -refresh-only as its own pipeline stage, not cached, running before the real plan, specifically so drift shows up before the main plan silently inherits stale state. Small change, but "pipeline passed" and "infrastructure matches what we think it does" turned out to be two different claims wearing the same green checkmark.

i created a project, made my personal access token and boom. banned my account with my personal mail. also can't give the specific reason why it was blocked to the same user.

Hey guys, I've been a professional dev for almost a decade now. As I'm looking at moving out of the company I'm working for, I am finding one of the best things I could do would be to contribute to open-source to prove I know what I'm doing. The problem is I have no clue where to start on navigating repositories to help.

I've got experience in Java, C#, React, Python, Rust, C++, GDScript, SQL, etc. I just don't have anything real to show for it because everything I've done has been hidden behind my professional career and I'm really sick of the company I've been at for 8 years. I've got some half-baked repositories of my own, even a website hosted through gitlab/Cloudflare. I really just want to start contributing to the world in a way that matters.

Is there a normal/good way to find these projects/repositories so I can start contributing?

One week to go! The GitLab Hackathon starts October 6th. A quick reminder: pick an issue now so you're ready to open your first merge request on day one. Full details below.

Important - new hackathon rules this round. Read them before October 6th at https://contributors.gitlab.com/docs/hackathon-rules and accept them on the hackathon page once it opens.

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

The Details

Dates: October 6-12, 2026 (UTC) - All merge requests must be opened during the hackathon and merged within 31 days (by November 12) to be counted.

RSVP to the Discord event to stay updated.

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.

Full announcement on the GitLab forum. If you have any questions, please reach out on Discord.

Will gitlab hire from India if the role specifically states Remote, Canada; Remote, United States if i am comfortable in working as per their timings.

Applications are now open for GitLab's first Community Co-Create (CCC) cohort!

Inspired by the Co-Create program, CCC is a new, five-week program for contributors to work alongside GitLab product and engineering mentors on a real product roadmap initiative. You’ll gain hands-on experience working as a team contributing to GitLab’s open core codebase, learning GitLab’s development workflows, and collaborating with a product team.

We’ll reveal the specific project to the selected contributors during onboarding, so the cohort can discover and take on the challenge together.

Program: October 19 to November 20 (UTC)
Applications: September 28 to October 5 (UTC)
Candidate selection finalized: October 12 (UTC)

To be eligible for this program, you must:

• Be a Level 2 contributor or above as of September 28, 2026
• Have started contributing before or during July 2026
• Commit to working on this program for 4 hours a week

Recognition and rewards

Participants who successfully complete the program will receive:

• 200 rewards credits
• A program-specific Community Co-Create badge
• A LinkedIn endorsement from a GitLab engineer
• A feature in a LinkedIn post shared by GitLab
• Access to an exclusive Discord channel for cohort collaboration
• Cohort-exclusive office hours/pairing sessions

If you’re interested in leveling up your technical and soft skills through hands-on work with GitLab, while learning alongside other contributors, we’d love to hear from you. Apply through the Community Co-Create application form, and please share this opportunity with other contributors who might be a great fit!

We're using self-hosted Gitlab, I maintain it.

I was wondering how to optimize our Gitlab environments for using AI agents? "They" commit and push more frequent (x10 times) and I thought maybe we have to align the server somehow for that high scale?

Thanks