I joined the October 2026 GitLab community hackathon with zero prior GitLab contributions. Two weeks later I sit in 4th place with 13 merge requests across gitlab-org/gitlab, the contributor platform app, and the container registry. Here's what worked, what didn't, and what I'd tell anyone starting today.
Start with the rules — literally
My score showed 0 for the first days despite open MRs. The fix: sign in at contributors.gitlab.com/hackathon and accept the hackathon rules. No acceptance, no points — it really is that binary. Second rule that matters: get assigned to an issue on the contributor platform before opening an MR, or the MR scores nothing. I made every MR traceable to an issue from then on.
Small, linked MRs beat big ones
My highest-effort work — a post-deployment migration deleting orphaned project group links (!259047) with database-reviewer back-and-forth on batch sizes and query plans — is still unmerged. Meanwhile these small ones all merged within days:
-
JSON 400 for malformed API bodies — one
rescue_from+ a request spec. - Rails logger to STDOUT in dev — a single initializer (after a reviewer proved my first approach would double-log in CI and I pivoted).
- Exact-one strings for scanner health counts and deduplicating bypassable security policies.
Each linked merged MR is worth ~130 points (20 created + 20 commits + 60 merged + 30 issue-linked). Four of those is 520+ points. Volume of merged small work is the whole game — open MRs score nothing until they land.
Reviewers are the bottleneck — manage them
Almost every delay I hit was a person, not code: maintainers OOO, 13-deep review queues, a security review with an internal-only verdict I couldn't even read. What helped:
-
Ping with context, not "bump". "Both threads addressed in
e5313f1c, pipeline green — could you re-review?" gets answers. - Answer every thread the same day. My fastest merge (!2860) went from review comment to fix to merge in about 5 hours.
- Docs-only MRs fly. Two of my quickest wins were single-paragraph doc fixes (#606169, scan policy precedence). Docs lint is fast and technical writers review quickly.
Find work where the labels are
The quick win label on gitlab-org/gitlab issues is a goldmine — I pulled 41 unassigned ones in one query. ESLint-violation issues in one codebase area (Duo Chat) are perfect batch work: same pattern, same reviewers, three MRs. And check assignees first — half the good ones are already taken by people running the same playbook.
The scoreboard, honestly
Top 3 from 4th needs ~3,300 more points, roughly 25 merged MRs at my current mix. The leaders got there differently: #1 banked 2,000 Translate points and 5,000+ Plan points. Code alone won't catch that — I'm adding translations and this post (content = 200 points) to the mix. Lesson: read the scoring rubric on day one, not day ten.
If you're on the fence about contributing: the community review culture is genuinely welcoming, the triage bots route you to reviewers automatically, and small fixes are celebrated. Just accept the rules first.
Top comments (0)