GitLens users rejoice! This release introduces exciting updates, including preview support for a browser-based editing experience in VS Code online, legendary new GitLens+ features like Worktrees and Visual File History, and more! Keep reading to see what’s new in GitLens 12.
What do Olympic speed skaters and developers have in common? They have a need…a need for speed. 😏 Nobody likes moving slow, no matter if you’re competing for the gold, or just trying to deploy an awesome new feature. The GitKraken team has been hard at work making sure all GitKraken Client users, especially macOS users, have the speediest experience possible when leveraging our legendary Git client to collaborate with teams.
Intro to the CLI – Part 1: Why Learn to Use The Terminal and Some History Long-time fans of GitKraken Client have come to love the graphical user interface, or GUI, that allows you to click on a Git branch or commit to perform an action or even drag and drop a branch to start a pull request. Version 8.0 of GitKraken Client introduced the GitKraken CLI, allowing you to interact with your repositories, and the rest of your computer, from Terminal Tabs.
Zip into Git Integration for Jira version 4.0! Our team has been whipping up some speedy new features and improvements to enhance your Git Integration for Jira Data Center and Jira Server experience. Do more in Git without leaving Jira, reducing context switching for a better workflow. Start using Git Integration for Jira free today! Start Free Trial.
We’re excited to share what’s new and improved in the v8.2 release of GitKraken Client. Even solo superheroes will benefit from Workspaces but we’ve made a lot of updates designed for Teams to get the most out of Git. So assemble your team and get ready to tackle even the largest projects in Git. Keep reading this article or watch the video below to see what’s new! We just can’t stop improving productivity with Git.
Before I introduce myself, I first want to highlight a monumental day in our company’s story. Today, we begin writing a new chapter under a new company name. We’ve decided to name the entire company after our flagship product, the ultra-popular GitKraken Client. Why make this move now? It’s much more than a cosmetic name change. Today ushers in the next phase in our evolution – one in which we will become the premier provider of Git tools for developers around the world.
For those of you who don’t know me, I’m Eric Amodio, creator of GitLens. I’m an innovator, leader, architect, and seasoned full-stack developer. I started developing GitLens way back in 2016 when I fell in love with Visual Studio Code and wanted to play with what was then newly released extension support. It all started with a simple question: could I add Git insights via CodeLens (hence GitLens) to any document? Which of course was yes, and a whole lot more.
If you’ve been building client websites for a while, you may remember a time before WordPress. A time when building websites meant creating every HTML page by hand. At some point, you probably decided that there were common features that every customer needed on their site, so you started using one customer’s website as the template for the next. Of course these days, WordPress is the underlying software for many modern websites, and there’s no need to re-invent core functionality.
If you’re writing or tracking code for a project you’ve likely heard of Version Control Systems, or VCS, also commonly referred to as source control. The primary function of a Version Control System is to host a project and track how it develops over time. With a VCS, developers can compare changes in files, track commits, propose changes, view project history, revert to old versions of the project, and more.
You groan. Perhaps not audibly, but your eyes widen and then slowly shut with dread. After a lucky streak of merging feature branches without incident, you finally hit a Git merge conflict. Unsure of where to start, you sheepishly bring up Slack and direct message a plea for help. Maybe this has been you, or maybe you’ve just seen it happen. Either way, it means spending time untangling the code by yourself, or with the sympathetic assistance of another.
