GitLens was developed in 2016 as a lightweight extension that supercharges the capabilities of Git within VS Code. Today, with over 14 million installs and counting, GitLens is the most popular Git extension in the VS Code marketplace and one of the most widely-used extensions overall. Millions of developers are leveraging GitLens to unlock helpful insights about their project history in VS Code.
GitKraken knows that software development relies on efficiently coordinating with your A-Team. That is why we’ve added a pull requests section, more repo information to GitKraken Workspaces and a new way to organize and share them with your teams in GitKraken Client! As Mr. Keif would say: I pity the tool that doesn’t have the incredible team features included in GitKraken Client v8.4!
Click below to read other articles from our CLI intro series: At the beginning of this series, we looked at the benefits of using the CLI shell on your machine. One of those benefits is the wide range of developer tools available that only have a CLI. In this part of the CLI intro series, we’re going to focus on.
In this article, we will cover how you can combine some of the most powerful tools available to developers–VS Code and Git–to start making meaningful contributions to both open source and private projects. Before we get into driving Git with VS Code let’s start with some background.
Git Integration for Jira Cloud has seen some major updates in the last quarter, including new data residency support for the EU and US regions and a BRAND NEW interface for Jira administrators: giving you more control over managing your integrations and repositories directly from Jira. Let’s dive into the new features and improvements for Git Integration for Jira Cloud.
While doing packaging for Icinga, I noticed we have a lot of YAML files describing GitLab pipelines doing very similar jobs. The same build job across different operating systems. That’s wasteful behaviour, which leads to a bigger workload when it comes to modifying these jobs. Tasks like adding new versions and especially adding new operating systems become tedious. What I’m looking for is a way to have interchangeable values for our building jobs.
In part 1 of the CLI Stands For…A CLI Into Series, we outline why you would want to use the CLI, some of the benefits of doing so, and a bit of CLI history and terminology. In part 2 – An Introduction to Shell Commands, get ready to roll up your sleeves and dive into a deeper understanding of the terminal.
