From 0966186e81374d82c1932a2bcf7a0610af9b5057 Mon Sep 17 00:00:00 2001 From: Gauvain Date: Tue, 7 Jul 2026 00:41:46 +0200 Subject: [PATCH] =?UTF-8?q?ci(pr-title):=20revert=20to=20pull=5Frequest=20?= =?UTF-8?q?=E2=80=94=20pull=5Frequest=5Ftarget=20can't=20run=20a=20workflo?= =?UTF-8?q?w=20new=20in=20the=20PR?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A pull_request_target workflow executes from the BASE branch, so pr-title.yml (added in this PR, absent on develop) never runs under it — leaving the required 'Validate PR Title' check stuck in Expected. Back to pull_request so the check runs from the PR branch. The fork-PR write-token improvement can be revisited in a follow-up once this workflow exists on develop. Keep the success() guard and the per-PR concurrency group. --- .github/workflows/pr-title.yml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/.github/workflows/pr-title.yml b/.github/workflows/pr-title.yml index 44766516..4f414490 100644 --- a/.github/workflows/pr-title.yml +++ b/.github/workflows/pr-title.yml @@ -1,19 +1,13 @@ name: 📝 PR Title -# pull_request_target so fork PRs get a write token — this workflow only reads -# the PR title and posts/updates a sticky comment; it never checks out or runs -# PR code, so it is not exposed to the usual _target code-execution risk. on: - pull_request_target: + pull_request: types: [opened, edited, synchronize, reopened] branches: [develop, master] permissions: contents: read -# Key on the PR number, not github.ref: under pull_request_target github.ref is -# the base branch (shared by every PR), which would collapse all PRs into one -# group and cross-cancel their title checks. concurrency: group: ${{ github.workflow }}-${{ github.event.pull_request.number }} cancel-in-progress: true