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 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 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

[Vinya567]

@greptileai

[greptile-apps]

Greptile Summary

This PR aligns the repository with the org-wide CI setup in triton-inference-server/.github, replacing per-repo workflow and hook implementations with thin caller stubs pinned to v1.4.3.

• conventional-pr.yml: New caller-stub workflow that validates PR titles against Conventional Commits and applies type labels via the org-wide reusable workflow. Correctly gates same-repo PRs on pull_request and fork PRs on pull_request_target (for write-token access to label) while scoping permissions to pull-requests: write, issues: write, contents: read — the reusable workflow never checks out PR code.
• pre-commit.yml: Migrates from pre-commit/action@v3.0.1 to a direct pip install + git diff | xargs invocation. Adds a pre-commit cache keyed on the config file hash, null-delimited path handling for filenames with spaces, --diff-filter=d to skip deleted files, and an explicit contents: read permission.
• .pre-commit-config.yaml: Adds default_install_hook_types: [pre-commit, commit-msg], a conventional-pre-commit commit-msg hook, fixes a whitespace bug in the flake8 --extend-ignore arg, and moves the add-license hook source from developer_tools to triton-inference-server/.github@v1.4.3.

Confidence Score: 5/5

Safe to merge — changes are CI/tooling configuration only, with no production code modified.

All three files contain CI workflow and pre-commit configuration. The pull_request_target routing pattern is implemented correctly (mutually exclusive conditions, no PR code checkout, scoped permissions). The pre-commit pipeline change handles edge cases (spaces in paths, deletion-only PRs) properly. Both the workflow and the hook config pin to the same tag (v1.4.3), which is self-consistent. No logic errors or security gaps were identified.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/conventional-pr.yml	New caller-stub workflow triggering the org-wide conventional-pr reusable workflow; correctly routes same-repo vs fork PRs to pull_request vs pull_request_target with scoped permissions and a pinned tag at v1.4.3.
.github/workflows/pre-commit.yml	Replaces pre-commit/action with direct pip install + git diff xargs approach; adds pre-commit cache, least-privilege permissions, null-delimited path handling, and deleted-file filtering.
.pre-commit-config.yaml	Adds default_install_hook_types for commit-msg stage, fixes flake8 arg quoting, adds conventional-pre-commit hook, and migrates add-license source from developer_tools to .github at v1.4.3.

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

[greptile-apps]

Version tag inconsistency with PR description

The PR description and checklist consistently reference v1.4.1 as the pinned tag (e.g. "Caller stub … @v1.4.1", "pinned tags current: v1.4.1 — already exist"), but the actual code pins v1.4.2 in both the workflow (@v1.4.2) and .pre-commit-config.yaml (rev: v1.4.2). The code is self-consistent, but the description would mislead anyone comparing it against the org .github repo. If v1.4.2 is intentional, the PR description should be updated to reflect it.

[mc-nv]

Fixed - documentation drift: the descriptions have been refreshed to the current pinned tag v1.4.3 (they lagged behind the tag revisions; the tag exists and CI is green fleet-wide).