'GitLab is a slam dunk': One team lead weighs his options

What this post added

This post details a team lead's experience and recommendation of GitLab, specifically highlighting its integrated CI/CD capabilities. The author discusses using GitLab for personal and professional projects, migrating a team from Subversion to Git and GitLab, and counseling others to switch. Key technical points include the benefits of decentralized Git/GitLab for distributed teams, the importance of short-lived merge requests for efficient code reviews, and the primary barrier to GitLab CI adoption being training and ingrained habits. The author also contrasts GitLab with other tools like GitHub and Bitbucket, emphasizing GitLab's open-source nature, integration of features (version control, bug tracker, kanban board, MR handling, CI), and self-hosting capabilities. The post also touches on the challenges of migrating large Subversion monorepos to Git and suggests GitLab could provide educational resources for such transitions.