Code-review

Beyond simple chat interactions, ChatGPT can understand code, suggest improvements, and even troubleshoot errors. With natural language processing at its core, it provides meaningful interactions that can be beneficial to developers.

Since its creation, GitLab has been a popular choice for its CI/CD and pipelines focus. GitHub, on the other hand, has been the go-to choice for its ease of use and popularity among developers. That's why, when I first started using GitLab two years ago, I felt a discrepencies between the two flows for reviewing code.

Learn about the top 10 code smells to watch out for in pull requests, with examples and tips for fixing them. Improve the quality of your code and avoid common coding mistakes with these practical tips.

Do you think you reviewers leave your pull requests unnoticed on purpose? Is continuously asking for code reviews creating a small but persistent nevrose in your day-to-day? Great! Let's list why your team sucks at reviewing pull requests, and what you can do to improve it (before quitting your job).

In this article, we will be going through the code review best practices in GitLab. If you are interesting in learning how to use GitLab to be more productive while reviewing code, follow us!

GitHub bots, sometimes referred to as GitHub Apps, are essentially bots that support the software development process on GitHub. These apps are first-class actors, so they can do just about any task on GitHub - sadly, they won't write code for you (yet). In this article, we will explain how to create a GitHub bots without using any specific language (you should be able to do it even if you work in Java, who knows?) and using the Probot framework on Node.js.

We’ve reviewed and selected the top 4 Discord GitHub bot for pull requests.

This article aims to help companies who want to survey their engineers to improve the developer experience in their engineering team. We developed this survey upon the recommendations of the SPACE framework, the four key DevOps metrics from Accelerate, and our own experience working with engineering teams through Axolo.

Cycle time may be measured in its most basic form by adding the time from the first commit to the time when the pull request is merged. In other terms, the rate at which you develop. Discover how to follow your cycle time and to reduce your code review time in our study!