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 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 redis_cache#24
• 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 repository with the org-wide CI setup in triton-inference-server/.github: it adds a thin conventional-pr caller workflow that delegates PR-title validation and type-labeling to the pinned reusable workflow at v1.4.3, rewrites pre-commit.yml to use null-delimited file lists (handling spaces and deleted files correctly), and extends .pre-commit-config.yaml with a commit-msg stage hook for local Conventional Commits validation while migrating the add-license hook to the centralized .github repository.

• conventional-pr.yml: Routes same-repo PRs through the safe pull_request event and fork PRs through pull_request_target (gated by a repo-identity condition), with only the minimum permissions needed for labeling and PR metadata reads.
• pre-commit.yml: Replaces the old pre-commit/action step with a direct pip install + null-delimited xargs pipeline; adds an actions/cache step keyed on the config hash and explicit contents: read permissions.
• .pre-commit-config.yaml: Adds default_install_hook_types, fixes the flake8 --extend-ignore= argument (removes a stray space that could misparse the flag), and swaps the add-license hook source from developer_tools to the org .github repo.

Confidence Score: 5/5

Safe to merge — all three files contain only CI/hook configuration with no functional code changes, and the pull_request_target usage is appropriately gated.

The changes are purely CI and pre-commit configuration. The pull_request_target event in conventional-pr.yml is constrained by a repo-identity condition and grants only the permissions needed for label management; the reusable workflow is pinned to a write-once tag in the same org. The pre-commit.yml improvements (null-delimited xargs, --diff-filter=d, caching) are strictly better than the previous implementation. The flake8 arg fix in .pre-commit-config.yaml removes a stray space that would have silently misparsed the --extend-ignore flag.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/conventional-pr.yml	New thin-caller workflow delegating PR-title validation and labeling to the org-wide reusable workflow at v1.4.3; pull_request_target for fork PRs is gated by a repo-identity condition with documented rationale.
.github/workflows/pre-commit.yml	Adds explicit least-privilege permissions, replaces pre-commit/action with direct pip install + null-delimited xargs, adds cache keyed on config hash, and filters deleted files with --diff-filter=d.
.pre-commit-config.yaml	Adds default_install_hook_types for commit-msg stage, fixes flake8 --extend-ignore= arg (removes stray space), adds conventional-pre-commit commit-msg hook, and migrates add-license hook to org-wide .github repo at v1.4.3.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant OrgWF as triton-inference-server/.github reusable workflows (v1.4.3)
    participant Repo as Repo Labels / PR

    Dev->>GH: Open / Edit PR
    GH->>GH: conventional-pr.yml triggers (pull_request for same-repo, pull_request_target for forks)
    GH->>OrgWF: "uses: conventional-pr.yml@v1.4.3 permissions: pull-requests:write, issues:write"
    OrgWF->>Repo: Read PR title + commit subjects
    OrgWF->>Repo: Validate Conventional Commits format
    OrgWF->>Repo: Apply type label (ci/feat/fix/...)

    Dev->>Dev: git commit
    Dev->>Dev: commit-msg hook runs (conventional-pre-commit v4.4.0)
    Dev->>Dev: pre-commit hooks run (isort, black, flake8, clang-format, codespell, pre-commit-hooks, add-license)

    Note over GH: pre-commit.yml (PR CI)
    GH->>GH: "git diff -z --diff-filter=d HEAD^1 HEAD"
    GH->>GH: xargs -0 pre-commit run --files
    GH->>OrgWF: add-license hook at v1.4.3

Loading

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

[Vinya567]

LGTM.

[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