1 views collected around this technical thread.
The latest release of Commit Check introduces two new capabilities—pr-comments, which automatically posts check results as Pull Request comments, and base-merge, which verifies that a branch is rebased onto the target branch—thereby improving PR review efficiency and CI pipeline enforcement.
This article explains the three common Git pull‑request merge strategies—Merge, Rebase, and Squash—detailing their advantages, disadvantages, and suitable scenarios, and provides practical recommendations for developers to choose the appropriate method when integrating code changes.
This article explains the importance of code review, outlines Google’s comprehensive code‑review rules, and provides practical steps—including process controls and automation—to help teams adopt effective review practices and improve software quality.
This tutorial explains how to configure Jenkins multibranch pipelines to automatically discover Git branches and pull‑requests, run conditional stages such as unit tests and code analysis, set up the required Jenkinsfile, configure GitHub webhooks, and troubleshoot common issues, providing a complete CI/CD workflow for developers.
This guide explains how to configure a Bitbucket webhook and a standard Jenkins job with the generic‑webhook‑trigger plugin to automatically receive pull‑request events, extract the PR ID, and trigger downstream actions without relying on a multi‑branch pipeline job.
This guide explains how to set up and use Jenkins multibranch pipelines—covering automatic branch and pull‑request discovery, conditional Jenkinsfile logic, GitHub webhook configuration, and troubleshooting—to create a fully automated CI/CD workflow for any Git‑based project.
The article outlines best practices for remote software teams to keep pull requests small, fast, and well‑communicated, emphasizing frequent reviews, clear labeling, context provision, reviewer support, CI automation, and a collaborative, non‑authoritative culture to improve code quality and team productivity.
This guide explains how to install the SonarQube Community Branch Plugin, configure multi‑branch scanning, and integrate pull‑request quality reports into GitLab CI pipelines using SonarQube settings and API commands.
This guide explains how to set up Bitbucket webhooks and Jenkins Bitbucket Branch Source plugin so that every Pull Request automatically triggers a Jenkins multi‑branch pipeline build, improving build speed and reliability.
The article explains how to use TFS release pipelines, environment variables, and feature‑branch pull requests to automatically provision isolated test environments for each PR, enabling end‑to‑end continuous delivery linked to user stories.
This article explains what a pull request is, why it is essential for code quality and collaboration, and walks through the typical four‑step workflow—creating a branch, opening a pull request, updating it, and completing the merge—using Git and TFS/VSTS examples.
This article introduces the Pull Request Diff Copy plugin for Visual Studio Team Services, explains its background, how it extracts incremental file differences during pull‑request builds, and details the automated CI/CD pipeline used to develop, test, and publish the extension, significantly reducing deployment time.
This article outlines a four‑part, enterprise‑focused Git tutorial that covers fundamentals, advanced workflows, corporate‑level practices, and branch‑strategy design, aiming to help development teams master version control, collaboration, and continuous delivery using tools like VSTS/TFS.
The TFS 2017 update introduces a completely redesigned branch page with a "mine" view, a revamped pull‑request UI featuring enhanced diff, comment, and file tracking capabilities, new squash‑merge support, improved build and commit traceability, Git LFS file preview, code‑link sharing, and additional UI enhancements for a smoother DevOps workflow.