From user, to advocate, to contributor: my GitLab journey

The author shares their journey of transitioning their IT development and support company, Tickett Enterprises Limited, from using SVN to adopting GitLab, detailing their experiences and improvements over several years. Initially using SVN in a basic form, the company faced challenges such as collaboration issues and code deployment uncertainties, prompting a switch to GitLab's Community Edition for better project management, branching, and collaboration. Over time, the author enhanced their processes by integrating GitLab CI for automation, developing custom project creation tools using GitLab's API, and participating in GitLab's community, including contributing to the GitLab-Triage project. They reflect on the learning curve, especially adapting to new tools and best practices, and share insights gained from attending GitLab Commit conferences, which highlighted GitLab's vast capabilities. The author actively contributes to the GitLab community and plans to explore further integrations and automations, such as transitioning their helpdesk operations to GitLab and implementing linting for code formatting. They express a desire to connect with other GitLab users to share knowledge and experiences, especially regarding .NET projects and customer billing solutions.

No tracked trend matches for this post yet.