The last of our three-part series on GitLab and Jira integrations offers a step-by-step look at how the tools work together. Read on
Learn how to use the Visual Studio code editor more efficiently and meet some of the GitLab contributors that made these new features happen.
Are you using manual jobs and needs relationship in your CI/CD pipeline? Learn more about the fix that might cause your pipeline to behave differently.
Stay agile by using GitLab for DevOps project management
How we used web component technologies like the Shadow DOM to make it easy to incrementally adopt our new design system, Slippers.
How we learned from our mistakes and adopted an iterative software development mentality to reduce the likelihood of shipping something that doesn't add value.
An overview of Ruby 2.7 heap compaction and the risks it adds to production Rails applications.
Learn about how GitLab users can employ GitOps to cover both Kubernetes and non-Kubernetes environments
Learn how to filter in JSON data structures and interact with the REST API. Use the GitLab API to lint your CI/CD configuration and dive into Git hooks speeding up your workflows.
Check out how to integrate GitLab self-managed with Atlassian Jira to connect your merge requests, branches, and commits to a Jira issue.
CI/CD variables are useful (and flexible) tools to control jobs and pipelines. We unpack everything you need to know about GitLab environment variables.
We asked for your most unexpected causes of bugs. Here's what we learned.
Check out how to use the GitLab App on the Atlassian Marketplace to connect your merge requests, branches, and commits to a Jira issue.
Massive merge requests lead to more problems than solutions. We explain how embracing iteration can lead to a better experience for the code author and code review.
We explain how to use patch files for better code review.
The best code reviews are empathetic and fair. We explain best practices for providing feedback.