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.
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.
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:
This feature was particularly fun to develop since I was part of the target audience!
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:
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:
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:
Some modification to make the Releases page more valuable:
As part of our effort to make Releases more useful, we added the ability to search for issues and merge requests by Release:
Every once in a while I step outside the boundaries of the Release Management group and fix something that bugs me: