From dbb73f8e68ae45edfb560d2b9718e2647a47da07 Mon Sep 17 00:00:00 2001 From: tebako-ci Date: Tue, 22 Sep 2026 18:34:20 +0800 Subject: [PATCH] ci(release-monitor): pin the onboarding commit surface via add-paths MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit create-pull-request commits the whole dirty tree by default. The 4.0.7 onboarding (#110) rode in with the runner's .bundle/config (bundler-cache writes a runner-local BUNDLE_PATH) and the monitor's own monitor-result.json summary — neither belongs on main (the 3.3.8 onboarding, #17, carried only versions.yml + patches/). Pin add-paths to exactly the onboarding surface: the version catalog and the patch tree. New per-version partition/overlay files land under patches/, so seeding stays covered; any future runner junk stays out. --- .github/workflows/release-monitor.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/release-monitor.yml b/.github/workflows/release-monitor.yml index ac594b4..43abd17 100644 --- a/.github/workflows/release-monitor.yml +++ b/.github/workflows/release-monitor.yml @@ -53,6 +53,12 @@ jobs: uses: peter-evans/create-pull-request@v7 with: branch: onboard/ruby-${{ matrix.version }} + # The onboarding surface is exactly the version catalog plus the + # patch tree — never the runner's .bundle/config (bundler-cache + # writes one) or the monitor-result.json run artifact. + add-paths: | + versions.yml + patches/ title: "Onboard ruby ${{ matrix.version }}" commit-message: "Onboard ruby ${{ matrix.version }} (release monitor)" body: |