Creating overhead with meetings and reviews is a risk to the efficiency and remote culture of organisations and should be actively avoided for an organisation to succeed remote at scale.
In GitLab 8.6 and up, you can subscribe to a label. Whenever an issue is tagged with the label you subscribed to, you will get a notification.
In this post we'll consider some ways people evaluate or represent productivity, and I ask for your thoughts on what you track and what you think matters.
Here we would like to share our thoughts about these issues and what we’re planning to do to make things better with GitLab.
At GitLab we'll tell you to make small merge requests, review and merge often. But in the real world, you have to build a complex feature that requires weeks and thousands of changes.
We want to give everyone that loves GitLab the opportunity to help shape its progress and be empowered to do this effortlessly.
This is a start in describing the workflow that we've established over the past year at GitLab.
All fields required
Find out which plan works best for your team
Learn about pricingLearn about what GitLab can do for your team
Talk to an expertSee what your team can do with the most comprehensive AI-powered DevSecOps platform.