Re: [RFC] Automating patch pushes to trunk via the bot

Project / Subsystem

gcc / gcc

Date

2026-09-24

Proposer

"Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

—/10

Technical tradeoffs

  • • Potential for errors if automation is not robust.
  • • Need to ensure all review and CI checks are properly integrated before merging.

All attributes

project
gcc
subsystem
gcc
patch_id
—
discussion_id
b1b8d4db-390e-4d00-a3d8-b157725dc941@arm.com
source_type
public_inbox
title
Re: [RFC] Automating patch pushes to trunk via the bot
headline
Automating patch pushes to trunk via the bot
tldr
A proposal to allow a bot to automatically push approved patches to the GCC trunk is being discussed, with considerations for existing workflows and potential…
proposer
"Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>
consensus
Proposed
outcome
proposed
sentiment_score
—
technical_tradeoffs
  • • Potential for errors if automation is not robust.
  • • Need to ensure all review and CI checks are properly integrated before merging.
series_id
—
series_role
standalone
series_parts
[]
tags
  • • automation
  • • workflow
  • • git
  • • contribution
bugzilla_url
—
date
2026-09-24T00:00:00.000Z

Re: [RFC] Automating patch pushes to trunk via the bot

Yuao Ma proposes enabling a bot to automatically push/merge approved patches to the GCC trunk, citing OpenJDK’s Skara bot as a precedent. This aims to streamline the contribution process by reducing manual interaction after code reviews. The discussion touches on the current workflow, the value proposition of using a web-based system for merging, and the need for more engagement with the forge.