My GitLab Contributions in a 🥜


One of the coolest things about working at GitLab is that every line of code I write is source-available, and most of it is open source.

The GitLab logo

As a result, my public contributions to GitLab serve as an unusually detailed record of my professional work:

Below are some of the highlights of my time at GitLab, complete with links to all the nitty-gritty details.

Merge trains

One of the most interesting features I helped build during my first year at GitLab is merge trains, a conceptually simple feature with a lot of behind-the-scenes complexity. I wrote the majority of the frontend code for this feature; here’s a list of all the merge train-related merge requests I put together:

GitLab Pages + Let’s Encrypt

This feature was particularly fun to develop since I was part of the target audience!

Releases page

Since I’m a part of the Release Management group, it should come as no surprise that I spend a lot of time modifying the Releases page.

Associating Releases to Milestones

As of GitLab 12.5, Releases can be associated with one or more Milestones. Developing this feature involved lots of small changes throughout the codebase:

Allow Releases to be created and edited through the UI

When I joined GitLab, Releases could only be created or modified using the Release API. This (still ongoing!) effort helped make Releases simpler to use:

Add a “dedicated” Release page

Originally, the only way to view GitLab Releases was on the Releases page, which showed all Releases for a given project. This feature added a new page — a Release page — that displayed a Release individually:

Releases page upgrades

Some modification to make the Releases page more valuable:

Release searching

As part of our effort to make Releases more useful, we added the ability to search for issues and merge requests by Release:

Quality of life

Every once in a while I step outside the boundaries of the Release Management group and fix something that bugs me: