# Pull Request

A proposal to merge code changes from one branch into another for discussion and review before integration.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Week Ending November 15, 2026

DevFeed: [Week Ending November 15, 2026](<https://devfeed.tech/articles/week-ending-november-15-2026-146591.md>)

Original publisher: [Read original article](<https://lwkd.info/2026/20261120>)

Published: 2026-11-20T12:22:32Z

Content type: news

Language: en

Sources: [Last Week in Kubernetes Development](<https://devfeed.tech/sources/last-week-in-kubernetes-development.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [Phoronix](<https://devfeed.tech/topics/phoronix.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cryptographic-verification](<https://devfeed.tech/tags/cryptographic-verification.md>), [design](<https://devfeed.tech/tags/design.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-news](<https://devfeed.tech/tags/developer-news.md>), [development](<https://devfeed.tech/tags/development.md>), [device](<https://devfeed.tech/tags/device.md>), [devices](<https://devfeed.tech/tags/devices.md>), [docs](<https://devfeed.tech/tags/docs.md>), [dra](<https://devfeed.tech/tags/dra.md>), [ephemeral](<https://devfeed.tech/tags/ephemeral.md>), [ephemeral-storage](<https://devfeed.tech/tags/ephemeral-storage.md>), [feature](<https://devfeed.tech/tags/feature.md>), [freeze](<https://devfeed.tech/tags/freeze.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

Kubernetes v1.38 releases now include signed SLSA provenance starting with v1.38.0-beta.0, enabling downstream cryptographic verification of release artifact builds. The v1.38 code freeze is in effect, with only release-blocking work considered for the milestone; critical enhancements require an exception. Development updates include alpha kubelet metrics for in-place Pod-level resource resizes and a scheduler benchmark for partitionable-device scoring. Separately, KEP-6386 proposes Pod-level ephemeral-storage requests and limits behind a feature gate, updating scheduling, quota, LimitRanger, and eviction handling while retaining existing storage accounting. Resizing is out of scope; the proposal targets Alpha in v1.38, Beta in v1.39, and Stable in v1.41.

### Source excerpt

Developer News

## Improvements on the pull request overview in public preview

DevFeed: [Improvements on the pull request overview in public preview](<https://devfeed.tech/articles/improvements-on-the-pull-request-overview-in-public-preview-144596.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-19-improvements-on-the-pull-request-overview-in-public-preview>)

Author: Allison

Published: 2026-11-20T00:02:21Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [attention](<https://devfeed.tech/tags/attention.md>), [better](<https://devfeed.tech/tags/better.md>), [collaboration-tools](<https://devfeed.tech/tags/collaboration-tools.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [compare](<https://devfeed.tech/tags/compare.md>), [context](<https://devfeed.tech/tags/context.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [failed](<https://devfeed.tech/tags/failed.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [merge](<https://devfeed.tech/tags/merge.md>), [optional](<https://devfeed.tech/tags/optional.md>), [overview](<https://devfeed.tech/tags/overview.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [status](<https://devfeed.tech/tags/status.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

GitHub's public preview of the pull request Overview page has been updated to clarify merge readiness and make common review tasks easier. Failed optional checks no longer make otherwise mergeable PRs appear blocked; missing requirements and next steps are clearer, and completed review threads collapse. Checks and approvals expand on click, while force-push activity links old and new commits and commit activity shows timestamps. The page also fixes mobile and layout issues, keeps branch names visible on small screens, and lets users edit Development sidebar links or lock and unlock conversations. Comments mentioning Copilot better explain the action and selected model before submission. Users can try the preview from the header and return to the classic overview through the same menu; the post invites feedback and issue reports.

### Source excerpt

Your feedback has helped improve the new pull request Overview page since its November 5, 2026 public preview. Here's what's new! Clearer merge status and next steps Failed optional checks... The post Improvements on the pull request overview in public preview appeared first on The GitHub Blog.

## What's new in AWS Transform - continuous modernization for re:Invent 2026

DevFeed: [What's new in AWS Transform - continuous modernization for re:Invent 2026](<https://devfeed.tech/articles/what-s-new-in-aws-transform-continuous-modernization-for-re-invent-2026-145206.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/whats-new-in-aws-transform-continuous-modernization-for-reinvent-2026/>)

Author: Nithin Moorthy

Published: 2026-11-19T23:01:00Z

Content type: release

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [code](<https://devfeed.tech/tags/code.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [health](<https://devfeed.tech/tags/health.md>), [integration](<https://devfeed.tech/tags/integration.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>), [repository](<https://devfeed.tech/tags/repository.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

AWS Transform continuous modernization now links AWS Health planned lifecycle events to affected repositories and findings, then applies a matching skill and opens one pull request per repository for most events. The AWS Health API integration requires Business Support+, Enterprise Support, or Unified Operations, with other listed support plans available in some Regions. Onboarding connects GitHub, GitLab, and Bitbucket via OAuth, creates an execution role, and recommends scheduled analyses. Findings sharing an underlying issue are grouped across repositories, and grouped remediations combine each repository's findings into one pull request. Teams can run custom analysis on AWS managed infrastructure or their own account; custom remediation runs in their own account. If no skill fits, a generated skill awaits review before use or publication. Chat can answer estate questions and perform actions after showing a confirmation card, using the user's permissions.

### Source excerpt

Ahead of re:Invent 2026, AWS Transform continuous modernization is faster to start, easier to act on, and easier to extend. A new AWS Health integration takes you from a planned lifecycle event straight to the affected code, and remediations now arrive as one clean pull request per repository.

## An Empirical Study of Visual Artifacts in Pull Request Descriptions

DevFeed: [An Empirical Study of Visual Artifacts in Pull Request Descriptions](<https://devfeed.tech/articles/an-empirical-study-of-visual-artifacts-in-pull-request-descriptions-142157.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23289>)

Author: Tianzi Hao, Kazi Amit Hasan, Yuan Tian, Bram Adams

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [artifacts](<https://devfeed.tech/tags/artifacts.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [code](<https://devfeed.tech/tags/code.md>), [content-type](<https://devfeed.tech/tags/content-type.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [error-messages](<https://devfeed.tech/tags/error-messages.md>), [gifs](<https://devfeed.tech/tags/gifs.md>), [github](<https://devfeed.tech/tags/github.md>), [images](<https://devfeed.tech/tags/images.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [interface](<https://devfeed.tech/tags/interface.md>), [labeling](<https://devfeed.tech/tags/labeling.md>), [logs](<https://devfeed.tech/tags/logs.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [study](<https://devfeed.tech/tags/study.md>), [taxonomies](<https://devfeed.tech/tags/taxonomies.md>), [ui](<https://devfeed.tech/tags/ui.md>), [user](<https://devfeed.tech/tags/user.md>), [videos](<https://devfeed.tech/tags/videos.md>)

### AI overview

The study finds that visual artifacts in GitHub pull request descriptions are associated with more scrutiny of user-facing behavior, but not faster reviews. In VisPR, 13.3% of 2,473,892 English, human-authored PRs from repositories where visuals were established practice included at least one artifact. Interaction and state dominated the labeled examples, especially in GIFs and videos; images more often included text such as logs or errors. Compared with matched non-visual PRs, visual PRs received 43% more review comments and 17% more reviewers, and took longer from first response to merge, though overall time to merge and churn-normalized review efficiency did not differ significantly. Review comments more often addressed UI appearance or behavior, and visual-output fixes after review were more common. These are reported associations, based on matched comparisons and LLM-assisted comment classification, not evidence that visuals caused the differences.

### Source excerpt

arXiv:2611.23289v1 Announce Type: new Abstract: Reviewers rely on pull request (PR) descriptions to understand what a change does, yet some changes, such as UI updates or runtime behavior, are hard to convey in text alone. PR authors attach visual artifacts to fill this gap, but how often they do so, what they show, and whether they change how a PR is reviewed remain unknown. We present a large-scale study of visual artifacts in GitHub PR descriptions. From 6,505,113 closed PRs in 5,012 repositories, we built VisPR, a dataset of 2,473,892 English, human-authored PRs from 647 repos where visual artifacts are an established practice. Of these, 329,185 (13.3%) are visual PRs, i.e., their descriptions contain at least one visual artifact (479,974 in total). By manually labeling a sample of 1,113 visual artifacts from 891 merged visual PRs, we derived two taxonomies: 11 content types capturing what developers show and six purposes capturing why they include visual artifacts. The dominant content type is Interaction & State, which shows how the interface responds to user actions. its share rises from 37.0% of images to 63.5% of GIFs and 79.7% of videos, whereas about a quarter of images (23.4%) show text such as logs, code, or error messages . Compared with 1,782 merged non-visual PRs matched on repository, PR type, and change size, visual PRs receive 43% more review comments and 17% more reviewers, and take 72% longer from first response to merge, time to merge and churn-normalized review efficiency do not differ significantly. LLM-assisted classification of 10,031 review comments in two groups shows that review centers on code in both, but comments on visual PRs address how the UI looks or behaves twice as often (6.4% vs.3.3%), and visual-output fixes after review are about four times as common (4.7% vs. 1.2% of PRs). Visual artifacts are thus associated with closer scrutiny of what users see, not with an overall faster review.

## Rotate a leaked GitLab token and let GitLab Duo fix the code

DevFeed: [Rotate a leaked GitLab token and let GitLab Duo fix the code](<https://devfeed.tech/articles/rotate-a-leaked-gitlab-token-and-let-gitlab-duo-fix-the-code-144779.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/secret-detection-token-rotate-and-fix/>)

Author: Mark Mishaev

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>)

Tags: [acting](<https://devfeed.tech/tags/acting.md>), [actions](<https://devfeed.tech/tags/actions.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [beta](<https://devfeed.tech/tags/beta.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [chat](<https://devfeed.tech/tags/chat.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code](<https://devfeed.tech/tags/code.md>), [duo](<https://devfeed.tech/tags/duo.md>), [features](<https://devfeed.tech/tags/features.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [let](<https://devfeed.tech/tags/let.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Starting with GitLab 19.6 beta for GitLab Ultimate, an active leaked GitLab PAT can be rotated from its vulnerability finding: GitLab revokes it, stores a replacement in Secrets Manager, and GitLab Duo opens an MR to update CI/CD jobs. The replacement value is not shown to the user or agent; rotation happens before the agent starts. Review and merge the MR, then resolve the finding. Rotation is immediate and irreversible, and the replacement is scoped to the current project, so scripts outside GitLab CI/CD or jobs in other projects need another token. The feature supports GitLab PATs, including fine-grained PATs, but not other detected secret types. GitLab.com users can rotate their own tokens; Self-Managed administrators can also rotate others' tokens. If the Duo session fails, rotation and secret storage still occur, leaving code updates manual. A dependency-free CLI can batch-rotate group findings and eligible CI/CD variable tokens; it defaults to dry-run, caps runs at 10 rotations unless configured, and omits token values from reports.

### Source excerpt

Secret detection alerts you when an active personal access token (PAT) is exposed in your default branch. Acting on that finding is harder: revoking the token breaks dependent pipelines, and replacing it safely takes several manual steps. While the finding waits in your vulnerability report, the token stays live. Starting in GitLab 19.6 in beta for GitLab Ultimate, you can remediate a leaked GitLab PAT directly from the vulnerability page. Select Rotate and fix, and GitLab revokes the token, stores a replacement in GitLab Secrets Manager, and uses GitLab Duo Agent Platform to open a merge request (MR) to update your CI/CD jobs. You review and merge the MR. GitLab never exposes the new token value to you or your agents. Why leaked tokens stay active after detection Imagine that secret detection flags an active PAT in deploy.sh: export GITLAB_TOKEN="glpat-..." Fixing this manually requires tracking down the token's owner, revoking it, generating a replacement with matching scopes, storing it securely, and opening MRs to update your scripts and CI/CD jobs. Because this process is tedious, remediations often stall or go wrong: The finding ages: Nobody wants to break the pipeline, so the finding sits in the vulnerability report while the token remains active. The fix stops halfway: Someone revokes the token immediately, breaking the build. In a rush to recover, they paste a replacement into a less secure CI/CD variable. The new token leaks: Someone shares the replacement token in a chat thread so a teammate can configure it. In the gap between detected and rotated, the token still works for anyone who can read the repository. Rotate and fix in a snap The Rotate and fix function closes this gap by combining secret detection and validity checks, GitLab Secrets Manager, and GitLab Duo Agent Platform. When you open an active PAT finding and select AI actions > Fix with AI > Rotate and fix, GitLab: Revokes the leaked token and creates a replacement with the same name, scopes,

## GitLab 19.6 released

DevFeed: [GitLab 19.6 released](<https://devfeed.tech/articles/gitlab-19-6-released-144780.md>)

Original publisher: [Read original article](<https://docs.gitlab.com/releases/19/gitlab-19-6-released/>)

Author: GitLab

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [1-5](<https://devfeed.tech/tags/1-5.md>), [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [added](<https://devfeed.tech/tags/added.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [availability](<https://devfeed.tech/tags/availability.md>), [duo](<https://devfeed.tech/tags/duo.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [slack](<https://devfeed.tech/tags/slack.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

GitLab 19.6 adds governance, agent workflows, faster merge request reviews, and security controls. MCP server tool calls now create audit events, while group Owners can deny tools, require approval, or allow them (the control is in beta). Duo in Slack is in limited availability on GitLab.com; `/goal` starts long-running Developer Flow sessions that can commit, push, and create merge requests without per-action approval, and scheduled automations are in beta. Rapid Diffs is generally available, streaming server-rendered diffs; the first file is reported to appear in about 1.5 seconds versus 4.5 seconds previously. Security updates include Rust scanning in Advanced SAST (added in 19.5 and still beta), malware rules for merge request approvals requiring SBOM-based dependency scanning, and configurable pipeline-variable limits. Web search in Agentic Chat is off by default and requires group or instance enablement; searches create audit events. The notes also flag upgrade guidance, including potential custom NGINX configuration breaks after the bundled version update.

### Source excerpt

GitLab 19.6 released with GitLab Duo in Slack in limited availability on GitLab.com

## Turn Slack conversations into trusted software, faster

DevFeed: [Turn Slack conversations into trusted software, faster](<https://devfeed.tech/articles/turn-slack-conversations-into-trusted-software-faster-144778.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-slack-integration-for-software-factory/>)

Author: Rebecca Carter

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [Slack](<https://devfeed.tech/topics/slack.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [also](<https://devfeed.tech/tags/also.md>), [best](<https://devfeed.tech/tags/best.md>), [can](<https://devfeed.tech/tags/can.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [capability](<https://devfeed.tech/tags/capability.md>), [channel](<https://devfeed.tech/tags/channel.md>), [commit](<https://devfeed.tech/tags/commit.md>), [context](<https://devfeed.tech/tags/context.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [customer](<https://devfeed.tech/tags/customer.md>), [decision](<https://devfeed.tech/tags/decision.md>), [delivered](<https://devfeed.tech/tags/delivered.md>), [faster](<https://devfeed.tech/tags/faster.md>), [features](<https://devfeed.tech/tags/features.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [product](<https://devfeed.tech/tags/product.md>), [slack](<https://devfeed.tech/tags/slack.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

GitLab for Slack lets users mention @GitLab in a channel or DM to turn discussion into tracked GitLab work and agent flows, then return results to Slack. It can read the surrounding messages in the channel where it was mentioned, summarize a channel, and surface GitLab context such as issues and merge request status. Requests run under the requester's linked GitLab account and existing permissions; the agent does not operate in external Slack Connect channels. Each request creates a GitLab agent session, and merge requests follow existing review, approval, and audit rules. Usage draws from GitLab Credits, which admins can track and cap. The agent acts only when asked in channels, and DM replies are private to the requester. The feature is generally available for GitLab.com users in GitLab 19.6; support for Self-Managed and Dedicated is planned for a later release.

### Source excerpt

Most software starts as a conversation: a customer requests a new capability, a product manager weighs it against the roadmap, an engineer checks feasibility, and a security lead asks what it touches. Then someone has to turn it into work. They reread the thread, retype the decisions into an issue, and hope they didn't miss an important detail buried in a reply. The conversation moves fast; the handoff between both teams and tools is where it slows. AI agents are uniquely equipped for that handoff: reading a long, many-voiced discussion and turning it into structured work. That leaves people free to collaborate while agents produce the output. GitLab for Slack now adds agentic capabilities and is generally available for GitLab.com users in GitLab 19.6, with support for GitLab Self-Managed and GitLab Dedicated to follow. Mention @GitLab in a thread in your team's channels, and the agent reads the conversation, finds what already exists, turns decisions into tracked work, and starts the agent flows that carry it to production. Work starts in Slack and lands in GitLab, where it's governed, tracked, and delivered. "Teams make decisions in Slack every day, and the best agents are the ones that can act on that context. GitLab for Slack lets agents read the conversation, take action across the software lifecycle in GitLab, and bring the results back to the thread. Teams can go from a quick discussion to planned, reviewed, and shipped work without switching tools." - Katie Steigman, Vice President Product Management, Slack Slack is the front door, GitLab does the work GitLab for Slack connects the interface where your team discusses the work to the platform where your software ships. Your team's conversation in Slack itself becomes the agent's input, so no decision gets lost between the thread and the first commit. The agent also looks beyond the thread. When you mention @GitLab, it can read the messages in the channel where you mentioned it, so its response reflects the wh

## Aikido's Deep Review finds Java4Shell in the PR that introduced it

DevFeed: [Aikido's Deep Review finds Java4Shell in the PR that introduced it](<https://devfeed.tech/articles/aikido-s-deep-review-finds-java4shell-in-the-pr-that-introduced-it-143872.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/deep-review-finds-java4shell-in-pr>)

Author: Debarshi

Published: 2026-11-18T19:04:00Z

Content type: news

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [software security audit](<https://devfeed.tech/topics/software-security-audit.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2021](<https://devfeed.tech/tags/2021.md>), [2026](<https://devfeed.tech/tags/2026.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [arm](<https://devfeed.tech/tags/arm.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [bug](<https://devfeed.tech/tags/bug.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [news](<https://devfeed.tech/tags/news.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [pr](<https://devfeed.tech/tags/pr.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [review](<https://devfeed.tech/tags/review.md>), [upstream](<https://devfeed.tech/tags/upstream.md>)

### AI overview

Aikido says Deep Review identified the Java4Shell flaw when run against a reconstruction of the 2021 OpenJDK pull request that introduced it. The excerpt explains that malformed Base64 padding could cause integer underflow in the AVX-512 decoder, producing an oversized write past the destination buffer; the vulnerable path is limited to x86-64 CPUs with AVX-512 VBMI support. Deep Review recommended falling back to the safer decoder when fewer than four input bytes remain, matching the upstream fix for this bug. It also reported two other defects, an oversized vector write and incomplete invalid-character validation, which the excerpt says were later corrected upstream. For mitigation, it recommends upgrading to listed patched Java releases; Aikido also offers patched Temurin 17 and 21 images for JDK and JRE use if upgrading is not yet possible, and describes dashboard and Attack Surface exposure checks.

### Source excerpt

We recreated the 2021 OpenJDK pull request behind Java4Shell (CVE-2026-114938) and ran Deep Review on it. It flagged the bug and suggested the upstream fix. Category: News

## Quoting Daniel Stenberg

DevFeed: [Quoting Daniel Stenberg](<https://devfeed.tech/articles/quoting-daniel-stenberg-140866.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Nov/18/daniel-stenberg/>)

Author: Simon Willison

Published: 2026-11-18T15:58:27Z

Content type: opinion

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [cURL](<https://devfeed.tech/topics/curl.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-2-329](<https://devfeed.tech/tags/ai-2-329.md>), [bugfixes](<https://devfeed.tech/tags/bugfixes.md>), [c](<https://devfeed.tech/tags/c.md>), [c-56](<https://devfeed.tech/tags/c-56.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coding-agents-268](<https://devfeed.tech/tags/coding-agents-268.md>), [curl](<https://devfeed.tech/tags/curl.md>), [curl-14](<https://devfeed.tech/tags/curl-14.md>), [daniel-stenberg](<https://devfeed.tech/tags/daniel-stenberg.md>), [daniel-stenberg-8](<https://devfeed.tech/tags/daniel-stenberg-8.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [generative-ai-2-067](<https://devfeed.tech/tags/generative-ai-2-067.md>), [llms](<https://devfeed.tech/tags/llms.md>), [llms-2-031](<https://devfeed.tech/tags/llms-2-031.md>), [rust](<https://devfeed.tech/tags/rust.md>), [rust-118](<https://devfeed.tech/tags/rust-118.md>), [security](<https://devfeed.tech/tags/security.md>), [security-647](<https://devfeed.tech/tags/security-647.md>), [vibe-porting](<https://devfeed.tech/tags/vibe-porting.md>), [vibe-porting-9](<https://devfeed.tech/tags/vibe-porting-9.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

While agents rewrote 185,000 lines of curl's C code into 340,000 lines of Rust over a little more than three weeks, the curl project merged more than 300 commits, including over 200 bug fixes and a few vulnerability fixes, according to Daniel Stenberg. He says the project made another 200 commits the following month and raises the question of whether the Rust clones will keep pace. The excerpt provides no further comparison of the clones.

### Source excerpt

During the time these agents converted 185,000 lines of C code into 340,000 lines of Rust code (I counted), we merged over 300 commits in the actual curl project. We actually improved curl during these a little more than three weeks. A little over 200 bugfixes actually. 200 bugfixes that none of those rust rewrites have. We also fixed a few vulnerabilities. In another month we have done another 200 and maybe fixed a few more vulnerabilities. Will these clones keep up? -- Daniel Stenberg, Actual curl rewrites in Rust Tags: daniel-stenberg, curl, rust, security, coding-agents, c, ai, llms, generative-ai, vibe-porting

## AI Made Writing Code Cheap. Getting It Reviewed Now Takes 5x Longer, Says LinearB's CEO

DevFeed: [AI Made Writing Code Cheap. Getting It Reviewed Now Takes 5x Longer, Says LinearB's CEO](<https://devfeed.tech/articles/ai-made-writing-code-cheap-getting-it-reviewed-now-takes-5x-longer-says-linearb-s-ceo-140467.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-made-writing-code-cheap-getting-it-reviewed-now-takes-5x-longer-says-linearbs-ceo?source=rss>)

Author: Ishan Pandey

Published: 2026-11-18T10:29:49Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [2016](<https://devfeed.tech/tags/2016.md>), [2019](<https://devfeed.tech/tags/2019.md>), [2022](<https://devfeed.tech/tags/2022.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [2027](<https://devfeed.tech/tags/2027.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-ml](<https://devfeed.tech/tags/ai-and-ml.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [business](<https://devfeed.tech/tags/business.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [context](<https://devfeed.tech/tags/context.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [linearb](<https://devfeed.tech/tags/linearb.md>), [ori-keren](<https://devfeed.tech/tags/ori-keren.md>), [return](<https://devfeed.tech/tags/return.md>), [review](<https://devfeed.tech/tags/review.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [software-review](<https://devfeed.tech/tags/software-review.md>), [technology](<https://devfeed.tech/tags/technology.md>), [writing](<https://devfeed.tech/tags/writing.md>), [writing-code](<https://devfeed.tech/tags/writing-code.md>)

### AI overview

LinearB's analysis says AI speeds code creation but shifts delays downstream: in its benchmarks of 8.1 million pull requests from 4,800 teams, agent-opened pull requests waited 17.6 hours for first review versus 3.4 hours for human ones, and AI-assisted changes were about 2.6 times larger. CEO Ori Keren says agents lack delivery and business context, so LinearB rebuilt its platform around a knowledge graph linking tickets, code, incidents, ownership and releases. Its planned agent skills use that context to guide effort by change risk and help determine where human review is needed. For AI return, Keren recommends measuring cost per effective delivered change--people and token spending divided by changes that merged, shipped and did not return as rework--and tracking model cost against code quality. He advises against using raw throughput or AI adoption rates as proof of return. The excerpt reports Emburse's cost per effective pull request fell about 35% over seven months as most of its code moved to AI; these are company-reported examples, not a guarantee of results.

### Source excerpt

LinearB CEO Ori Keren on why AI code waits longer for review, how boards should judge AI's return and why context now steers coding agents.

## GitHub CLI 2.105.0

DevFeed: [GitHub CLI 2.105.0](<https://devfeed.tech/articles/github-cli-2-105-0-140394.md>)

Original publisher: [Read original article](<https://github.com/cli/cli/releases/tag/v2.105.0>)

Author: github-actions\[bot\]

Published: 2026-11-18T00:25:23Z

Content type: release

Language: en

Sources: [GitHub CLI](<https://devfeed.tech/sources/github-cli.md>)

Topics: [GitHub CLI extension](<https://devfeed.tech/topics/gh-extension.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>)

Tags: [event](<https://devfeed.tech/tags/event.md>), [event-streams](<https://devfeed.tech/tags/event-streams.md>), [github](<https://devfeed.tech/tags/github.md>), [github-cli](<https://devfeed.tech/tags/github-cli.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pull-request-review](<https://devfeed.tech/tags/pull-request-review.md>), [subscription](<https://devfeed.tech/tags/subscription.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>)

### AI overview

GitHub CLI 2.105.0 adds the preview `gh event` commands so scripts, integrations, and agents can wait for pull request changes instead of polling. `gh event listen` prints CloudEvent JSON, exits after the first event by default, and can wait for multiple events with `--count` or continue with `--follow`. Supported events include submitted reviews, pull request state and head changes, merge conflicts, and completed check suites; subscription commands create, list, view, and delete subscriptions. The release also improves stream framing, `Retry-After` handling, event output timing, and deleted-subscription error reporting. GitHub Event Streams is in preview.

### Source excerpt

What's Changed Subscribe to GitHub Event Streams with gh event (preview) The new gh event command set lets agents, integrations, and scripts wait for pull request changes instead of polling GitHub: # Wait for a review event gh event listen --resource https://github.com/OWNER/REPO/pull/NUMBER --event com.github.pull_request.review.submitted.v1 --timeout 30m # Wait for a check suite completion event gh event listen --resource https://github.com/OWNER/REPO/pull/NUMBER --event com.github.pull_request.check_suite.status.changed.v1 --jq .data.conclusion # List active event subscriptions gh event subscription list By default, gh event listen exits after the first event. Use --count to wait for several events or --follow to keep listening. Events are printed as CloudEvent JSON objects, with data.api_url pointing to the resource that changed. Supported events include submitted reviews, pull request state and head changes, merge conflicts, and completed check suites. The subscription create, list, view, and delete commands manage subscriptions directly. Note GitHub Event Streams is in preview. Join the wait list, read the announcement, or see the Event Streams documentation. What's Changed ✨ Features Add a server-sent events reader and Event Subscriptions API client by @babakks in #15071 Add gh event listen to wait for pull request events without polling by @babakks in #15072 Add gh event subscription list by @babakks in #15073 Add gh event subscription create by @babakks in #15074 Add gh event subscription view by @babakks in #15075 Add gh event subscription delete by @babakks in #15076 Suggest gh event listen to agents using gh pr and gh api by @babakks in #15077 Support check suite events and suggest them from gh run view and gh run watch by @babakks in #15081 🐛 Fixes fix(event listen): print each event without waiting for the next heartbeat by @babakks and @iancanderson in #15079 fix(event listen): report deleted subscriptions clearly by @babakks in #15080 fix(event): imp

## Improved governance for your docs: reviews and expanded roles

DevFeed: [Improved governance for your docs: reviews and expanded roles](<https://devfeed.tech/articles/improved-governance-for-your-docs-reviews-and-expanded-roles-141885.md>)

Original publisher: [Read original article](<https://www.mintlify.com/blog/improved-governance>)

Author: David Isquick

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [Mintlify Blog](<https://devfeed.tech/sources/mintlify-blog.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [docs](<https://devfeed.tech/tags/docs.md>), [editor](<https://devfeed.tech/tags/editor.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [governance](<https://devfeed.tech/tags/governance.md>), [live](<https://devfeed.tech/tags/live.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [roles](<https://devfeed.tech/tags/roles.md>)

### AI overview

Mintlify Enterprise adds editor-based review and expanded roles for controlling who can write, approve, and publish. Teams can keep reviewing through GitHub pull requests or request reviews in Mintlify, where reviewers inspect a diff and approve; only a publisher or admin can then publish. Requiring review disables auto publish. Admins can set approval counts and require reapproval after edits. On GitHub deployment branches with branch protection, reviews move to a branch, publishing requires review, and a reviewer with a connected GitHub account also approves the pull request; GitHub merge checks still apply. Without branch protection, admins can publish their own changes without review. New built-in roles include owner, publisher, and commenter; owners and admins can create custom roles, and roles can differ by site. Review requirements are in beta, require a GitHub docs repo, and are available on Enterprise; GitLab and Bitbucket support is in development.

### Source excerpt

Mintlify Enterprise now has stronger governance built into the editor. Require a review before any change goes live, and use expanded roles to control who can write, approve, and publish.

## wasmCloud 2.12.2: Host directories for plugins, and scanners that gate merges

DevFeed: [wasmCloud 2.12.2: Host directories for plugins, and scanners that gate merges](<https://devfeed.tech/articles/wasmcloud-2-12-2-host-directories-for-plugins-and-scanners-that-gate-merges-144206.md>)

Original publisher: [Read original article](<https://wasmcloud.com/blog/wasmcloud-2-12-2-release/>)

Author: Eric Gregory

Published: 2026-11-18T00:00:00Z

Content type: release

Language: en

Sources: [wasmCloud](<https://devfeed.tech/sources/wasmcloud-blog.md>)

Topics: [wasmCloud](<https://devfeed.tech/topics/wasmcloud.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [codeql](<https://devfeed.tech/tags/codeql.md>), [directories](<https://devfeed.tech/tags/directories.md>), [gate](<https://devfeed.tech/tags/gate.md>), [host-memory](<https://devfeed.tech/tags/host-memory.md>), [memory](<https://devfeed.tech/tags/memory.md>), [merge](<https://devfeed.tech/tags/merge.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [scanners](<https://devfeed.tech/tags/scanners.md>), [tables](<https://devfeed.tech/tags/tables.md>), [wasmcloud](<https://devfeed.tech/tags/wasmcloud.md>)

### AI overview

wasmCloud 2.12.2 adds host-directory mounts for component plugins, faster placement when hosts become ready, and page-table accounting in the host memory guard. Plugin filesystems remain opt-in: only hostPath volumes are supported, paths are validated, host reserved paths stay protected, and workload hostPath mounts cannot expose plugin directories. The release also makes OSV-Scanner lockfile findings and selected CodeQL alerts merge-blocking, with written malicious-dependency and remediation policies. Linux memory readings will be higher because VmPTE and, on 4.x kernels, VmPMD are counted; hosts unable to detect capacity now fail closed unless given an explicit limit or `off`. Before upgrading, apply the updated CRDs and check mount paths and hosts near memory thresholds. The excerpt also reports opt-in mimalloc/jemalloc throughput gains with modest per-workload memory increases, and digest-based caching for components lacking a digest.

### Source excerpt

wasmCloud 2.12.2 lets a host component plugin mount directories from the host, puts OSV-Scanner and CodeQL in front of every merge, counts page tables in the host memory guard, and places a waiting workload the moment a host turns ready.

## Git Clone vs Fork: Stop Mixing Them Up

DevFeed: [Git Clone vs Fork: Stop Mixing Them Up](<https://devfeed.tech/articles/git-clone-vs-fork-stop-mixing-them-up-138690.md>)

Original publisher: [Read original article](<https://hackernoon.com/git-clone-vs-fork-stop-mixing-them-up?source=rss>)

Author: William

Published: 2026-11-17T22:59:04Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [beginner](<https://devfeed.tech/tags/beginner.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cli](<https://devfeed.tech/tags/cli.md>), [clone](<https://devfeed.tech/tags/clone.md>), [commit](<https://devfeed.tech/tags/commit.md>), [communities](<https://devfeed.tech/tags/communities.md>), [contributing-to-open-source](<https://devfeed.tech/tags/contributing-to-open-source.md>), [fork](<https://devfeed.tech/tags/fork.md>), [forks-explained](<https://devfeed.tech/tags/forks-explained.md>), [git](<https://devfeed.tech/tags/git.md>), [git-clone](<https://devfeed.tech/tags/git-clone.md>), [git-vs-fork](<https://devfeed.tech/tags/git-vs-fork.md>), [github](<https://devfeed.tech/tags/github.md>), [github-cli](<https://devfeed.tech/tags/github-cli.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [governance](<https://devfeed.tech/tags/governance.md>), [gpl](<https://devfeed.tech/tags/gpl.md>), [license](<https://devfeed.tech/tags/license.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-foundation](<https://devfeed.tech/tags/linux-foundation.md>), [local](<https://devfeed.tech/tags/local.md>), [merge](<https://devfeed.tech/tags/merge.md>), [mistakes](<https://devfeed.tech/tags/mistakes.md>), [mit](<https://devfeed.tech/tags/mit.md>), [when-to-fork](<https://devfeed.tech/tags/when-to-fork.md>)

### AI overview

Clone is a Git command that copies a repository to your machine; fork is a GitHub or GitLab feature that creates a server-side copy in your account, where you can push changes when you lack write access to the original. For contributions, fork the project, clone your fork, add the original as the `upstream` remote, make changes on a branch, push to `origin`, and open a pull request. Forks do not update automatically: sync through GitHub's Sync fork, `gh repo sync`, or by fetching `upstream`, merging its `main` into your local `main`, and pushing to `origin`. The excerpt also notes that forks carry the original project's license, with examples of OpenTofu and Valkey developing separate governance and open licenses after upstream license changes.

### Source excerpt

Differentiating between git clone and git fork

## Track Copilot code review outcomes in Repository insights

DevFeed: [Track Copilot code review outcomes in Repository insights](<https://devfeed.tech/articles/track-copilot-code-review-outcomes-in-repository-insights-139404.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-17-track-copilot-code-review-outcomes-in-repository-insights>)

Author: Allison

Published: 2026-11-17T18:00:35Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [account-management](<https://devfeed.tech/tags/account-management.md>), [api](<https://devfeed.tech/tags/api.md>), [billing](<https://devfeed.tech/tags/billing.md>), [categories](<https://devfeed.tech/tags/categories.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [copilot-code](<https://devfeed.tech/tags/copilot-code.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-management-tools](<https://devfeed.tech/tags/enterprise-management-tools.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [insights](<https://devfeed.tech/tags/insights.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [reports](<https://devfeed.tech/tags/reports.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [request](<https://devfeed.tech/tags/request.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

Repository insights adds a page in each repository's Insights tab that summarizes Copilot code review outcomes: comments and high-severity comments addressed, reviewed pull requests without a later human change request, and merged pull requests that lacked Copilot review. It also provides the addressed rate with its numerator, denominator, unevaluable exclusions, trend, and supported breakdowns, plus comment categories. The same metrics are available in enterprise and organization `repos-1-day` reports through the Copilot usage metrics API. Repository viewers can access the page; API reports require an eligible owner, billing manager, or custom role with `View Copilot Metrics`. The Copilot usage metrics policy must be enabled.

### Source excerpt

You can now see how Copilot code review feedback lands in each repository. A new "Repository insights" page, the first item in a repository's Insights tab, brings Copilot code review... The post Track Copilot code review outcomes in Repository insights appeared first on The GitHub Blog.

## Building a gated review pipeline for AI coding agents on AWS

DevFeed: [Building a gated review pipeline for AI coding agents on AWS](<https://devfeed.tech/articles/building-a-gated-review-pipeline-for-ai-coding-agents-on-aws-139358.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/building-a-gated-review-pipeline-for-ai-coding-agents-on-aws/>)

Author: Owen Hawkins

Published: 2026-11-17T17:29:01Z

Content type: article

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>)

Tags: [acceptance-rate](<https://devfeed.tech/tags/acceptance-rate.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent-hooks](<https://devfeed.tech/tags/agent-hooks.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-knowledge-bases](<https://devfeed.tech/tags/amazon-bedrock-knowledge-bases.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-sns](<https://devfeed.tech/tags/amazon-sns.md>), [application-security-testing](<https://devfeed.tech/tags/application-security-testing.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [policy](<https://devfeed.tech/tags/policy.md>), [review](<https://devfeed.tech/tags/review.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

The article proposes a six-control pipeline to manage the review bottleneck created by AI coding agents: centralize versioned standards; run deterministic checks with bounded agent self-correction; use a diverse AI review panel whose findings are checked against code and semantically verified; apply risk-tiered merge policy in a deterministic gate; preserve human approval with review depth matched to risk; and validate generated tests and operational recommendations after merge. On AWS, it maps these controls to services including AgentCore, CodeBuild, S3, Lambda, CodePipeline, EventBridge, and Athena. The panel advises but does not approve or block; humans retain consequential decisions. Rollout starts with a four-week quality baseline, then deterministic gates, an advisory panel, and only later blocking policy after findings earn trust. Measure review time alongside defect escape, rework, stability, panel quality, change size, and cost, since faster decisions alone may not improve quality.

### Source excerpt

AI coding agents generate code faster than humans can review it. This post lays out a gated review pipeline of six controls that pairs deterministic checks with a verified AI review panel, applies risk-tiered policy gates, and keeps humans in charge of every consequential decision, with a concrete AWS implementation for each control.

## Agents didn't break code review, they exposed it

DevFeed: [Agents didn't break code review, they exposed it](<https://devfeed.tech/articles/agents-didn-t-break-code-review-they-exposed-it-140703.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/ai-code-verification-has-to-scale-past-the-human-reviewer/>)

Author: Brooks Naylor

Published: 2026-11-17T14:00:00Z

Content type: article

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code-verification](<https://devfeed.tech/tags/ai-code-verification.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [code-verification](<https://devfeed.tech/tags/code-verification.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [llm](<https://devfeed.tech/tags/llm.md>), [scale](<https://devfeed.tech/tags/scale.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

As agents increase the volume of code, delivery pressure can leave changes insufficiently reviewed, while large pull requests already made human approval an unreliable safeguard. John Crickett argues that neither human review nor an LLM should be the sole quality gate: LLM review is cheap and repeatable but inconsistent, so it adds value as one layer rather than as the final authority. He recommends pairing it with deterministic checks--static analysis, compiler checks, tests, and exploratory testing. These checks can consistently verify rules such as syntax, data flows, architecture, and dependencies; agentic verification can reason about intent and business logic that rules cannot establish. The layers should run independently of the code-generating agent and leave auditable evidence of intent, standards, checks, and results. The text also notes that even excellent code can implement the wrong requirement, so code quality alone does not establish that a system meets its intended needs.

### Source excerpt

Human review can't keep pace with agents. Learn how AI code verification pairs LLM review with deterministic analysis to scale, with John Crickett.

## AI Cannot Review What Humans Catch: A First Look at the Reviews of Agent Instruction Files

DevFeed: [AI Cannot Review What Humans Catch: A First Look at the Reviews of Agent Instruction Files](<https://devfeed.tech/articles/ai-cannot-review-what-humans-catch-a-first-look-at-the-reviews-of-agent-instruction-files-137967.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18582>)

Author: Wenhao Yang, Runzhi He, Minghui Zhou

Published: 2026-11-17T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [human review](<https://devfeed.tech/topics/human-review.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [act](<https://devfeed.tech/tags/act.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attention](<https://devfeed.tech/tags/attention.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [categories](<https://devfeed.tech/tags/categories.md>), [change](<https://devfeed.tech/tags/change.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [files](<https://devfeed.tech/tags/files.md>), [first](<https://devfeed.tech/tags/first.md>), [first-look](<https://devfeed.tech/tags/first-look.md>), [humans](<https://devfeed.tech/tags/humans.md>), [look](<https://devfeed.tech/tags/look.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>)

### AI overview

Across 2,870 instruction-file pull requests from 2,246 repositories, over 70% received no substantive review. The study treats files such as AGENTS.md, CLAUDE.md, .cursorrules, and SKILL.md as executable policy that can redirect agent behavior, while lacking the automated checks available for code. It reports a 16-category taxonomy of review concerns and a benchmark of 1,962 human-checked concerns across 468 pull requests. Tested against that benchmark with full repository access, Codex, OpenCode, and Claude Code recovered only 1.3-3.9% of concerns raised by humans; the abstract says they catch surface structure but miss factual errors, necessity, and staleness. The findings suggest these agents cannot replace human attention in reviewing instruction-file changes.

### Source excerpt

arXiv:2611.18582v1 Announce Type: new Abstract: Agents increasingly shape software, and instruction files steer them. Files such as AGENTS.md, CLAUDE.md, .cursorrules, and SKILL.md act as executable policy: prose that a machine reads and acts on. Unlike ordinary documentation, a single edit to one of these files can silently redirect how an agent behaves across an entire repository. Natural-language rules have no per-change oracle, so they slip past the compilers, type-checkers, and test suites that guard code. Review is therefore the only quality gate, but no prior work has studied how that review happens. We analyzed 2,870 instruction-file pull requests across 2,246 repositories. The gate is largely broken: over 70% of instruction-file changes receive no substantive review. When an AI reviewer substitutes for a human, it is structurally blind to the concerns that most need human judgment. It catches surface structure but misses factual errors, necessity questions, and staleness problems. We contribute the first taxonomy of instruction-file review concerns (16 categories), which exposes this sharp human/AI divergence, and a benchmark of 1,962 human-checked concerns across 468 PRs. We ran three widely-used agents (Codex, OpenCode, and Claude Code) against the benchmark, giving each reviewer the full repository at review time. They recovered only 1.3-3.9% of the concerns humans raise. Even the strongest current agents cannot substitute for human attention on these files.

## Where AI Use Is Normalized, Author Seniority but Not AI Disclosure Biases Code Review

DevFeed: [Where AI Use Is Normalized, Author Seniority but Not AI Disclosure Biases Code Review](<https://devfeed.tech/articles/where-ai-use-is-normalized-author-seniority-but-not-ai-disclosure-biases-code-review-137958.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18572>)

Author: Jenna Butler, Emerson Murphy-Hill, Constance Hadley, Alexa Tipton, Nancy Baym, Sankeerti Haniyur, Jina Suh

Published: 2026-11-17T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-disclosure](<https://devfeed.tech/tags/ai-disclosure.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [bias](<https://devfeed.tech/tags/bias.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [commit](<https://devfeed.tech/tags/commit.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [display](<https://devfeed.tech/tags/display.md>), [effectiveness](<https://devfeed.tech/tags/effectiveness.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [information](<https://devfeed.tech/tags/information.md>), [review](<https://devfeed.tech/tags/review.md>)

### AI overview

In a within-subjects experiment at an organization where AI use was normalized, 447 software engineers reviewed four code snippets with AI-use disclosure and author-seniority labels shown in commit messages. Disclosure did not bias perceived code effectiveness or author competence, while seniority labels significantly biased both. The result indicates no detected penalty for disclosed AI use in this setting; it does not establish that disclosure has no effect in other settings.

### Source excerpt

arXiv:2611.18572v1 Announce Type: new Abstract: Code-review tools increasingly display whether an author used AI when preparing pull requests. Recent studies report that AI disclosure makes reviewers rate otherwise identical work as less competent, with the penalty falling hardest on already-marginalized authors. In a within-subjects experiment in an AI-normalized organization, 447 software engineers each reviewed the same four code snippets under an AI-use disclosure embedded in the commit message and author-seniority labels. AI disclosure did not bias perceptions of code effectiveness or author competence, whereas a seniority label significantly biased both. Together, these findings show no detected penalty for disclosed AI use in this setting, while confirming that the author information shown in code review can still bias evaluations.

## Reliable Mining of Heterogeneous AI Coding-Agent Data: Context-Aware Prediction and Resource-Aware Ranking

DevFeed: [Reliable Mining of Heterogeneous AI Coding-Agent Data: Context-Aware Prediction and Resource-Aware Ranking](<https://devfeed.tech/articles/reliable-mining-of-heterogeneous-ai-coding-agent-data-context-aware-prediction-and-resource-aware-ranking-138000.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.20297>)

Author: Haoran Yu, Lifei Liu, Danping Zhang

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Data analysis](<https://devfeed.tech/topics/data-analysis.md>), [scikit-learn](<https://devfeed.tech/topics/scikit-learn.md>), [Operations research and optimization](<https://devfeed.tech/topics/operations-research-and-optimization.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [aipw](<https://devfeed.tech/tags/aipw.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [association](<https://devfeed.tech/tags/association.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [mining](<https://devfeed.tech/tags/mining.md>), [prediction](<https://devfeed.tech/tags/prediction.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [resource](<https://devfeed.tech/tags/resource.md>)

### AI overview

Across 71,677 pull requests from six AI coding agents, pooling records can reverse observed relationships: PRs with a co-authorship trailer had a 55.6% merge rate versus 77.5% without, but excluding the dominant agent reversed the gap. Conditioning on source, environment, and workflow raised gradient-boosting merge-prediction AUC from 0.774 to 0.832, with gains in temporal and unseen-repository evaluations; adjusted analysis found no stable trailer association. A creation-time-only model performed less well, especially temporally. A separate retrospective analysis estimated a 12.3-point gain from resource-aware allocation at a 30% budget, just 0.5 points above risk ranking. This is decision support over observed metadata, not evidence that assigning human review causes better outcomes.

### Source excerpt

arXiv:2611.20297v1 Announce Type: new Abstract: Operational records from AI coding agents differ across agents, repositories, tasks, and workflows. We study 71,677 pull requests (PRs) from six agents and show that pooling these records can reverse descriptive and predictive conclusions. PRs carrying a co-authorship trailer have a 55.6% merge rate, compared with 77.5% without the trailer, but removing the dominant agent flips this -21.8 percentage-point gap to +23.7 points. We treat this Simpson-type reversal as a data-veracity problem and represent source, environment, and workflow context in a feature cascade. Gradient-boosting merge-prediction AUC increases from 0.774 to 0.832; the advantage persists under temporal evaluation (0.801) and unseen repositories (0.807). The co-authorship coefficient changes from -1.09 to +1.44 after conditioning, whereas repository-clustered AIPW intervals show no stable adjusted trailer association. A strict PR-creation-time model reaches 0.741 AUC in standard evaluation and 0.710 on unseen repositories, although its temporal AUC falls to 0.641. Finally, a separately cross-fitted analysis of an observed-mode functional estimates a +12.3-point doubly robust gain at a 30% allocation budget on the non-Codex population, only 0.5 points above risk ranking. This last result is retrospective decision support over metadata states, not a causal effect of assigning human review.

## Loop Engineering: Version-Bound, Evidence-Gated Coordination for Production Coding Agents

DevFeed: [Loop Engineering: Version-Bound, Evidence-Gated Coordination for Production Coding Agents](<https://devfeed.tech/articles/loop-engineering-version-bound-evidence-gated-coordination-for-production-coding-agents-137957.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18571>)

Author: Yupeng Pang, Meiling Chen, Yang Yang, Wei Fu

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-loops](<https://devfeed.tech/tags/agent-loops.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-design](<https://devfeed.tech/tags/ai-design.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automated](<https://devfeed.tech/tags/automated.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [commit](<https://devfeed.tech/tags/commit.md>), [context](<https://devfeed.tech/tags/context.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [loop-engineering](<https://devfeed.tech/tags/loop-engineering.md>), [production](<https://devfeed.tech/tags/production.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Loop Engineering coordinates asynchronous coding-agent work through shared auditable repository state. Each loop defines a trigger, context projection, authority boundary, verifier, stop condition, and write-back rule; versioned Skills encode policy, a Harness limits actions and collects evidence, and human gates approve consequential transitions against exact artifact versions. In a production study at MewDesign, five specialized loops handled planning, implementation, review, test release, and reconciliation. Of five pull requests reaching a version-bound test lock, three advanced to test releases with runtime evidence from sources separate from deployment requests, while two stopped before merge. In one drift episode, a new commit invalidated prior approval and evidence, so stale continuous-integration results were not reused. This design-and-experience study is not a controlled benchmark and does not establish causal productivity or general safety; it offers early evidence of feasibility and traceability in one production setting.

### Source excerpt

arXiv:2611.18571v1 Announce Type: new Abstract: Coding agents can edit repositories and execute tests, yet production software work extends far beyond code generation. It requires durable task context, scoped authority, version-aware approval, source-independent verification, interruption recovery, and accountable handoffs between humans and automated workers. We present Loop Engineering, a method for operating multiple asynchronous agent loops over shared, auditable repository state without relying on private conversational handoffs. Each loop is specified by six elements: a trigger, a context projection, an authority boundary, a verifier, a stop condition, and a write-back rule. Versioned procedural contracts, called Skills, encode reusable operating policy; a Harness bounds the available action surface and collects evidence; human gates authorize high-consequence transitions against exact artifact versions. We report a design-and-experience study from MewDesign, a revenue-generating commercial AI design product. Five specialized loops cover planning, scoped implementation, review, test release, and reconciliation. A cross-sectional audit contains 50 durable marker records across 26 GitHub work items. Five pull requests reached a version-bound test lock: three proceeded to test releases with runtime evidence from sources distinct from the deployment request, and two stopped before merge. A detailed drift episode shows one observed fail-closed path: a new commit invalidated prior approval and evidence, and the workflow refused to reuse stale continuous-integration results. The study is not a controlled benchmark and does not establish causal productivity or general safety. It provides early evidence of feasibility, traceability, and bounded progression in one production setting.

## Level Up! AI-Driven Challenges and Adaptations to Code Review Practices

DevFeed: [Level Up! AI-Driven Challenges and Adaptations to Code Review Practices](<https://devfeed.tech/articles/level-up-ai-driven-challenges-and-adaptations-to-code-review-practices-137975.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18939>)

Author: Kaia Newman, Christian Bird, Jenna Butler, Emerson Murphy-Hill

Published: 2026-11-17T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attention](<https://devfeed.tech/tags/attention.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [can](<https://devfeed.tech/tags/can.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [company](<https://devfeed.tech/tags/company.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [practices](<https://devfeed.tech/tags/practices.md>), [review](<https://devfeed.tech/tags/review.md>), [up](<https://devfeed.tech/tags/up.md>)

### AI overview

A mixed-methods study at a large multinational software company (24 interviews and a 2,590-person survey) found that AI-assisted coding shifts reviewers toward design and intent while adding review burden through reduced author stewardship and larger or more numerous pull requests, with potential downstream debt. Use of AI for review was not correlated with less difficulty keeping up with pull request volume, so it alone did not resolve the challenge. Developers identified organizational support and resourcing for review, moving review work upstream, and focusing reviewer attention on the most important concerns as useful strategies.

### Source excerpt

arXiv:2611.18939v1 Announce Type: new Abstract: AI can write code faster than humans can review, causing a bottleneck and necessitating changes to code review practices. This bottleneck is hotly debated, giving rise to two extreme and orthogonal imagined futures: one where humans continue to be firmly entrenched in the review process, and one where AI agents merge pull requests entirely without human involvement. Yet, these futures remain rooted in folk wisdom. Through a mixed-methods study of interviews ($n = 24$) and a survey ($n = 2{,}590$) at a large, multinational software company with widespread access to AI, we identify AI-driven code review challenges and strategies reported as effective to meet them. We found that AI enables, necessitates, and complicates a shift in the human reviewer's role toward high-level concerns (e.g., design and intent). We found that AI-assisted authoring results in increased burden for reviewers due to challenges such as a lack of author stewardship and PR volume and size, potentially leading to downstream debt. Our survey showed AI review usage was not correlated with less difficulty keeping up with PR volume, indicating using AI for review alone is not sufficient for solving AI-driven review challenges. Developers found the most useful strategies to be organizations supporting and resourcing review, pushing review burden upstream, and prioritizing reviewer attention on the concerns that matter most.

## Refactoring English: Month 23

DevFeed: [Refactoring English: Month 23](<https://devfeed.tech/articles/refactoring-english-month-23-138125.md>)

Original publisher: [Read original article](<https://mtlynch.io/retrospectives/2026/11/>)

Author: Michael Lynch

Published: 2026-11-17T00:00:00Z

Content type: article

Language: en

Sources: [Mtlynch](<https://devfeed.tech/sources/mtlynch-io.md>)

Topics: [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [codex](<https://devfeed.tech/topics/codex.md>)

Tags: [book](<https://devfeed.tech/tags/book.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [effective](<https://devfeed.tech/tags/effective.md>), [english](<https://devfeed.tech/tags/english.md>), [goals](<https://devfeed.tech/tags/goals.md>), [here](<https://devfeed.tech/tags/here.md>), [heres](<https://devfeed.tech/tags/heres.md>), [highlights](<https://devfeed.tech/tags/highlights.md>), [i](<https://devfeed.tech/tags/i.md>), [indie](<https://devfeed.tech/tags/indie.md>), [life](<https://devfeed.tech/tags/life.md>), [lightweight](<https://devfeed.tech/tags/lightweight.md>), [like](<https://devfeed.tech/tags/like.md>), [more](<https://devfeed.tech/tags/more.md>), [my](<https://devfeed.tech/tags/my.md>), [one](<https://devfeed.tech/tags/one.md>), [project](<https://devfeed.tech/tags/project.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [retrospective](<https://devfeed.tech/tags/retrospective.md>)

### AI overview

Michael is weighing whether to keep marketing Refactoring English or move to another project after launching the book. October sales were $3.6k, including $2.2k during launch week; he says sustaining that level may require frequent blog posts and luck, and is considering author interviews, which he enjoyed but found labor-intensive. He is also trying shorter monthly retrospectives: they take up much of his writing time, often run late, and may bury useful standalone posts, while focusing on unresolved problems feels more clarifying than recounting past events. His completed work included most typography fixes and a blog post on Go test patterns. On coding agents, he describes VM-based environments, separate agent profiles that switch OpenCode v2 to cheaper models for simple tasks, an AFK mode, and using Claude Code through OpenCode for cross-vendor reviews.

### Source excerpt

New here? Hi, I'm Michael. I'm a software developer and founder of small, indie tech businesses. I'm currently working on a book called Refactoring English: Effective Writing for Software Developers. Every month, I publish a retrospective like this one to share how things are going with my book and my professional life overall. Highlights I'm debating between doubling down on my book or transitioning to another project. I'm experimenting with more lightweight retrospectives. Goal grades At the start of each month, I declare what I'd like to accomplish. Here's how I did against those goals:

## Introducing Insights Agent

DevFeed: [Introducing Insights Agent](<https://devfeed.tech/articles/introducing-insights-agent-139723.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/introducing-insights-agent>)

Author: Enrique Gonzalez

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud-agents](<https://devfeed.tech/tags/cloud-agents.md>), [code](<https://devfeed.tech/tags/code.md>), [connect](<https://devfeed.tech/tags/connect.md>), [cursor-origin](<https://devfeed.tech/tags/cursor-origin.md>), [insights](<https://devfeed.tech/tags/insights.md>), [product](<https://devfeed.tech/tags/product.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [queries](<https://devfeed.tech/tags/queries.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

PlanetScale Insights Agent investigates database performance issues using a database's schema, Query Insights data, and connected repository, then opens a pull request when evidence supports a change. Its two focused run types address slow queries and recommendations; runs can be started on demand or scheduled, and may propose changes across multiple files. It follows repository conventions, and Vitess runs can also open a deploy request. Changes are suggestions: nothing is automatically merged or deployed. Runs are billed when completed, with organization spend limits available; the temporary sandbox exists only during a run. PlanetScale's built-in agent offers curated prompts and managed setup, while the CLI and MCP server let teams build their own automations with custom prompts and more control. At launch, one GitHub or Cursor Origin repository can connect to each database. The feature is on by default but acts only after a repository is connected.

### Source excerpt

Insights Agent connect to your codebase to turn slow queries and schema recommendations into pull requests.

[Next page](<https://devfeed.tech/topics/pull-request.md?cursor=WyIyMDI2LTExLTE3VDAwOjAwOjAwKzAwOjAwIiwgIjk0OGI4NTFiLWM1ZTMtNDY2YS1hN2RmLTE1NWU0ZjVkYWRmYiJd>)