June 2022 Summaries

Software quality assurance engineers specialize in deep testing, defect detection, usability, and quality control, while developers primarily build software and can perform basic or automated testing but may lack the same testing perspective. Whether a team needs a dedicated QA professional depends on project complexity, required security and quality levels, team size, developer expertise, and the time available for testing; smaller or simpler projects may rely on developers, whereas larger, higher-risk products benefit from specialized QA. Teams without QA staff can use developer-led practices such as static code analysis, unit, integration, end-to-end, and code-review testing, along with structured defect management that identifies, prioritizes, fixes, verifies, and reports issues. Quality should also be evaluated through attributes including functionality, reliability, maintainability, usability, efficiency, security, and portability, supported by techniques such as audits, inspections, simulations, standardization, and stress testing. Git-based collaboration tools such as GitKraken Client are presented as aids for pull-request reviews, repository coordination, and merge-conflict detection, helping teams reduce risk and maintain code quality regardless of whether they employ dedicated QA engineers.

Git Integration for Jira connects Jira projects with GitHub repositories, enabling development teams to link code activity to Jira issues and manage selected GitHub workflows from within Jira. After installing the Marketplace app and authenticating through GitHub OAuth or a personal access token, users can connect one or multiple repositories. The integration supports smart commits, which use issue keys and commands in commit messages to add comments, log time, transition issues, or assign work, subject to relevant permissions and configuration. Users can also create issue-linked branches and pull requests through Jira’s Git Development panel, then view associated commits, branches, and pull request statuses in an issue’s details. For Jira Cloud and Server deployments, webhook-based indexing triggers can be configured in GitHub to reindex repositories when events such as commits or branch creation occur, helping keep repository information synchronized with Jira.

GitLens 12.1 expands its Visual Studio Code integration with richer GitLab.com support, linking merge requests, issues, avatars, and related details to annotations, hovers, status bar blame, branches, and commits, while paid GitLens+ plans now support GitLab Self-Managed repositories. The release also adds native Gerrit integration, customizable autolinks for external tools such as Jira and Zendesk, and an interactive rebase editor option for changing commit display order. Annotation improvements include clearer File Heatmap visualizations that emphasize newer code and fade older lines, along with File Changes highlighting to more easily identify added or modified lines. GitLens also promotes its free GitLens+ account, which includes features such as Worktrees and Visual File History, and invites community feedback through its GitHub issue tracker.

GitKraken Client v8.6 introduces performance and usability updates aimed at developers managing large or multi-repository projects. The release improves Git LFS clone and checkout operations by an estimated two to ten times through optimized handling of large files, while also enhancing branch checkout and graph responsiveness for repositories with many stashes. It adds Bitbucket Server Workspace support, enabling users to view and act on related repositories and pull requests from one location, and offers repository and terminal-tab aliases for easier navigation. Other additions include automatic issue linking in pull requests when branch names begin with integrated issue IDs, options to skip submodule updates globally or per repository, Git Bash as a Windows GitKraken CLI shell option, and a setting to limit displayed commits in the graph to as few as 500 for improved performance.

GitKraken announced GitKon 2022, a free virtual conference on collaboration for Git users of all experience levels, scheduled for October 11–13 and themed “Creating a Collaborative Future.” Building on the inaugural 2021 event, which drew more than 4,000 registrants, the conference will adopt a shorter format with sessions limited to 15 minutes and three-hour daily programs, while recorded sessions will remain available on demand. The first day will cover Git fundamentals, internals, and integrations; the second will focus on DevOps, GitOps, security, and distributed-team collaboration; and the third will target technology leaders with discussions on scaling teams, developer productivity, DORA metrics, and emerging trends. Live attendees can engage with speakers through the GitKon Discord server, and prospective presenters are invited to submit talks related to Git, DevOps, teams, and the event’s collaboration theme.

Choosing between Git monorepositories and multirepositories depends on an organization’s size, engineering culture, resources, codebase complexity, and changing needs rather than a universally superior model. A monorepo stores multiple projects in one repository, improving visibility, code reuse, standardization, cross-team collaboration, and broad refactoring, but it can create technical performance problems, long build times, unclear ownership, tight coupling, and wider consequences from faulty changes without substantial tooling and governance. A multi-repo model separates code into smaller repositories, providing clearer ownership, isolated failures, simpler access control, and more manageable workflows for smaller or less integrated teams, though it can increase administrative overhead, complicate cross-project changes and dependencies, and encourage silos as an organization expands. Large companies may use either approach at different stages of growth, while many organizations adopt hybrid structures; repository-management tools can also help teams coordinate work across multiple repositories.