ci: align pre-commit hooks and GitHub templates

[mc-nv]

What does the PR do?

Aligns this repository with the org-wide setup consolidated in triton-inference-server/.github:

• .pre-commit-config.yaml: shared baseline hooks, conventional-commit message validation (commit-msg stage), and the centralized add-license hook from the org .github repository (rev: v1.4.3 — excludes .github/ templates, never rewrites LICENSE files).
• Pre-commit CI runs only on files modified by the PR.
• Caller stub for the org-wide reusable conventional-pr workflow (@v1.4.3): validates the PR title against Conventional Commits (hard gate — it becomes the squash-merge commit), derives one human-readable label per distinct type found in the title and all conforming commit subjects (e.g. ci: → CI/CD, feat: → feature, fix: → fix), enforces org-wide label colors/descriptions, detects cherry-picks, and fails if no type is derivable and no type label is assigned.
• No per-repo templates: PR templates and issue routing are inherited from the org-wide defaults in triton-inference-server/.github (issues route to the server repository).

Depends on triton-inference-server/.github#5 (pinned tags current: v1.4.3 — already exist, CI is green).

Pros / Cons

Pros

• Single home (org .github repo) for hooks, templates, issue routing, and the PR-title workflow — one change propagates everywhere.
• Repos carry only a config file and two small workflow stubs; no template copies to drift.
• Commit/PR title format enforced both locally (commit-msg hook) and in CI (reusable workflow), with automatic type labels.
• License hooks never modify LICENSE files.

Cons / risks

• Version-pinned dependency on the org .github repository (tags are write-once; changes ship as a new tag + rev bump).
• Template inheritance requires the org .github repository to remain public.

Related Issues / PRs

• Resolves: TRI-1100

Related PRs:

• ci: migrate the centralized add-license hook to the org .github repository developer_tools#61
• ci: align pre-commit hooks and GitHub templates core#517
• ci: align pre-commit hooks and GitHub templates common#161
• ci: align pre-commit hooks and GitHub templates backend#127
• ci: align pre-commit hooks and GitHub templates python_backend#449
• ci: align pre-commit hooks and GitHub templates tensorrt_backend#124
• ci: align pre-commit hooks and GitHub templates onnxruntime_backend#351
• ci: align pre-commit hooks and GitHub templates pytorch_backend#200
• ci: align pre-commit hooks and GitHub templates openvino_backend#119
• ci: align pre-commit hooks and GitHub templates identity_backend#36
• ci: align pre-commit hooks and GitHub templates checksum_repository_agent#14
• ci: align pre-commit hooks and GitHub templates local_cache#16
• ci: align pre-commit hooks and GitHub templates repeat_backend#19
• ci: align pre-commit hooks and GitHub templates square_backend#22
• ci: align pre-commit hooks and GitHub templates third_party#80
• ci: align pre-commit hooks and GitHub templates triton_cli#127
• ci: align pre-commit hooks and GitHub templates tutorials#158
• ci: align pre-commit hooks and GitHub templates server#8890
• ci: align pre-commit hooks and GitHub templates client#909
• ci: align pre-commit hooks and GitHub templates tensorrtllm_backend#861
• ci: align pre-commit hooks and GitHub templates vllm_backend#133
• ci: align pre-commit hooks and GitHub templates perf_analyzer#467
• chore: never modify the COPYRIGHT template and guard .github templates model_analyzer#1032

Test plan

• pre-commit validate-config passes; pre-commit run --files <PR diff> passes locally with the centralized hooks pinned to the .github branch SHA.
• After .github#5 merges and v1.4.3 exists: the conventional-pr check validates this PR's own title and applies the ci label.
• No LICENSE file content is changed by this PR.

Caveats

• None beyond the merge-order note above.

Checklist

• PR title follows <commit_type>: <Title> (conventional commit)
• I ran pre-commit locally on all files changed by this PR and it passes
• Copyright header is correct on all changed files
• External contributors: I have read the Contribution guidelines and signed the Contributor License Agreement

[Vinya567]

@greptileai

[greptile-apps]

Greptile Summary

This PR aligns the redis_cache repository with the org-wide CI standards from triton-inference-server/.github, adding two new workflow stubs and updating the pre-commit configuration.

• conventional-pr.yml: A thin caller workflow that delegates PR-title validation and label management to the org-wide reusable workflow at v1.4.3, with an if: guard that routes same-repo PRs through the safe pull_request event and fork PRs through pull_request_target (write token needed for labeling, safe because the callee never executes PR code).
• pre-commit.yml: Replaces the pre-commit/action with a manual step that diffs only the PR-modified files using git diff -z | xargs -0, adds a cache step for the pre-commit environment, and restricts permissions to contents: read.
• .pre-commit-config.yaml: Adds default_install_hook_types, a conventional-pre-commit commit-msg hook, and the org-wide add-license hook (pinned to v1.4.3); also fixes the flake8 --extend-ignore argument quoting.

Confidence Score: 5/5

Safe to merge — all changes are CI/configuration files with no impact on the cache plugin's runtime behavior.

The PR adds two thin workflow stubs and updates pre-commit config. The pull_request_target guard is correctly constructed to avoid running elevated-permission jobs on same-repo PRs. The null-delimited xargs pipeline, cache step, and add-license hook are all straightforward and well-commented.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/conventional-pr.yml	New thin-caller workflow delegating to org-wide reusable workflow at v1.4.3; if: guard correctly isolates pull_request vs pull_request_target for same-repo vs fork PRs.
.github/workflows/pre-commit.yml	Updated to run pre-commit only on PR-modified files using null-delimited xargs, adds pre-commit cache step, and restricts to contents:read permission.
.pre-commit-config.yaml	Adds commit-msg hook type, conventional-pre-commit hook at v4.4.0, org-wide add-license hook at v1.4.3, and fixes flake8 arg quoting.
LICENSE	Copyright year updated from 2022 to 2022-2026; no substantive content changed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    PR[Pull Request Event] --> Q1{Same-repo or fork?}
    Q1 -->|Same-repo| PE[pull_request event]
    Q1 -->|Fork| PTE[pull_request_target event]
    PE --> IF1{if: head.repo == github.repository}
    PTE --> IF2{if: head.repo != github.repository}
    IF1 -->|true| CW[conventional-pr reusable workflow at v1.4.3]
    IF2 -->|true| CW
    IF1 -->|false| SKIP1[job skipped]
    IF2 -->|false| SKIP2[job skipped]
    CW --> LABEL[Apply type label]
    CW --> VALIDATE[Validate PR title]
    PR --> PC[pre-commit workflow]
    PC --> DIFF[git diff -z HEAD^1 HEAD]
    DIFF --> XARGS[xargs -0 pre-commit run --files]
    XARGS --> HOOKS[Run hooks on changed files only]

Loading

_{Reviews (2): Last reviewed commit: "ci: harden CI workflows and configs per ..." | Re-trigger Greptile}

[mc-nv]

Closing: the team is moving away from centralized org-level configuration in favor of per-repository self-contained setups (see triton-inference-server/server#8897 for the first decentralized implementation). Branch retained for reference. TRI-1100