May 2022 Summaries

GitLens is a widely used Visual Studio Code extension that enhances Git workflows by showing authorship details, revision history, and contextual blame information directly in the editor. The article describes several advanced customization options, including configuring blame hovers to display commit details across annotations or full lines of code, adjusting date formats and locales, and assigning custom keyboard shortcuts to frequently used GitLens commands. It also explains how users can control Git CodeLens displays, which present Git information within source files, and use formatting tokens to tailor current-line and status-bar blame annotations by changing their content, order, and message length. These settings are accessed primarily through the VS Code command palette and GitLens settings interface, allowing developers to adapt the extension’s interface and behavior to their individual workflows. The article also promotes the free GitLens+ offering, highlighting features such as Worktrees and Visual File History.

Shell customization in Zsh and Bash is primarily managed through configuration files such as ~/.zshrc and ~/.bashrc, which are loaded for common interactive, non-login terminal sessions, while login sessions may use files such as ~/.zshprofile. The article distinguishes interactive shells, which accept user input, from non-interactive shells used by scripts and programs, and explains how login status affects which configuration files are read. It shows how users can personalize prompts by modifying Zsh’s PROMPT variable or Bash’s PS1 variable to display dynamic details such as dates, directories, and hostnames, including adding color in Zsh or using external theme engines. It also describes aliases as shortcuts for frequently used commands, with examples for listing hidden files, making file deletion interactive by default, and simplifying Git commands, while cautioning that aliases can override existing command behavior. Finally, it notes that configuration files can run any commands whenever a new shell opens, such as displaying the current directory and its contents, and positions these customization skills as preparation for shell scripting and automation.

GitKraken Client v8.5 adds Azure DevOps repository support to GitKraken Workspaces, enabling developers to group related repositories in one view, review pull requests, access repository details, and take actions without switching between tools. The release also brings interactive rebasing to GitKraken CLI through the `gk rebase` command and introduces “Take current” and “Take incoming” shortcuts for resolving merge conflicts directly from the Commit Panel. Workspace enhancements include sharing repositories with organizational teams, a dedicated repository details icon, GitHub-style pull request search syntax, and filters for personal, at-risk, and repository-specific pull requests, with support varying by hosting provider. Team management has also been streamlined by allowing members to be added during team creation and sorting team views by username, while GitKraken Client remains available for Windows, macOS, and Linux.

Git Integration for Jira Data Center introduced expanded Automation for Jira support, allowing teams with both apps installed to trigger Jira actions from branch, commit, and pull request events, such as creating issues, updating statuses, assigning work, or adding comments. The update also adds repository breadcrumbs showing remote owners or groups to help distinguish repositories and forks, while Atlassian-approved security and performance testing confirms the app meets Data Center scalability requirements. Administrators using GitHub integrations can now enforce personal access token verification through secure mode before users can view repository development data, with support for GitLab, Azure DevOps, and AWS CodeCommit planned. Additional improvements include the ability to designate dedicated Data Center nodes for indexing jobs and support for SSH configuration files, and users are encouraged to update to the latest version to access these features.

GitKraken expanded its developer-tool suite through acquisitions to include the desktop GitKraken Client, the GitLens extension for VS Code, and Git Integration for Jira, aiming to reduce context switching and improve Git collaboration. Core functionality remains free for public repositories and, in GitLens, for public and local repositories, while paid tiers extend support to private and self-hosted repositories, integrations, administration, and collaboration features. GitKraken Client offers Pro for individuals or small teams at $4.95 per user monthly, Teams for up to 100 users across 10 teams at $8.95, and Enterprise for larger organizations at $18.95 with unlimited teams and enhanced license-management options. GitLens+ similarly provides Pro, Teams, and Enterprise plans priced at $1.95, $3.95, and $6.95 per user monthly, respectively, with private-repository access, team organization, support, and planned enterprise capabilities such as single sign-on. Bundled GitKraken Client and GitLens+ subscriptions offer discounts, while Git Integration for Jira is sold through the Atlassian Marketplace based on Jira seats; existing customers with more than 10 licenses will retain their plans and pricing until renewal while plan changes are reviewed.