Why do GitLab designers contribute to the codebase?
Mar 17, 2021Austin Regnery

Summary
This post details how designers at GitLab contribute to the codebase by setting up their development environments (GDK, GitPod), migrating UI components (e.g., buttons), and submitting merge requests for UI changes. It highlights the development of shared empathy through direct code interaction, the diversification of skill sets by learning frontend frameworks and contributing code, and the use of merge requests for proposing specific changes. The author also mentions contributing to new features like 'UX reviewer/maintainer to Danger bot' and 'shortcut for collapsible section markdown'.
More from the Issue and Merge Request Workflow Enhancements trail
- Agile planning gets a boost from new features in GitLab 18.10
- How we reduced MR review time with Value Stream Management
- Tutorial: Integrate GitLab Merge Request approvals with external systems
- How visualization improves the GitLab merge train experience
- Unveiling a new epic experience for improved Agile planning