Repository navigation
52 lines (47 loc) · 2 KB
/
Copy pathpr-title-normalizer.yml
File metadata and controls
52 lines (47 loc) · 2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
#
# @Project: gitmulti
# @Filename: /.github/workflows/pr-title-normalizer.yml
# @Date: 2026-05-22T00:00:00-07:00 (1779433200)
# @Author: Nate Corcoran <CLDMV>
# @Email: <Shinrai@users.noreply.github.com>
# -----
# @Last modified by: Nate Corcoran <CLDMV> (Shinrai@users.noreply.github.com)
# @Last modified time: 2026-10-02T11:30:31-07:00 (1790965831)
# -----
# @Copyright: Copyright (c) 2013-2026 Catalyzed Motivation Inc. All rights reserved.
#
# Individual repo: .github/workflows/pr-title-normalizer.yml
#
# Normalize contributor PR titles to Conventional Commits format, derived from
# the highest-priority commit in the PR. The release flow expects this shape, so
# a v4 repo wants this enabled. (Also backportable to v3 repos — the underlying
# action shipped in v3.3.0; it owns all skip logic: bot authors, the
# long-running release PRs, titles already starting with `release:`, and titles
# that already conform.)
#
# Thin caller: all job logic lives in the reusable, pinned at @v4. Bumping the
# pin carries fixes without editing this file.
name: 🏷️ PR Title Normalizer
# SECURITY NOTE: pull_request_target runs in the BASE repo's context with WRITE
# permissions and access to secrets. SAFE — the reusable's path is API-only (it
# never checks out or executes PR content). Triggers on opened + synchronize
# only (NOT edited): a maintainer hand-editing the title must not kick off a
# re-normalize loop.
on:
pull_request_target:
types: [opened, synchronize]
concurrency:
group: pr-title-normalizer-${{ github.event.pull_request.number }}
cancel-in-progress: true
permissions:
contents: read
jobs:
normalize:
permissions:
contents: read
pull-requests: write
uses: CLDMV/.github/.github/workflows/workflow-pr-title-normalizer.yml@v4
secrets:
# Map your repo/org secrets to the expected names.
BOT_APP_CLIENT_ID: ${{ secrets.CLDMV_BOT_APP_CLIENT_ID }}
BOT_APP_PRIVATE_KEY: ${{ secrets.CLDMV_BOT_APP_PRIVATE_KEY }}