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 redis_cache#24
• ci: align pre-commit hooks and GitHub templates repeat_backend#19
• 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/CD setup by introducing a thin-caller conventional-pr workflow, refactoring the pre-commit workflow to run only on PR-modified files, and updating .pre-commit-config.yaml with conventional-commit validation and the centralized add-license hook.

• conventional-pr.yml: New workflow that delegates all logic to the reusable org workflow at v1.4.3; correctly gates pull_request for same-repo PRs and pull_request_target (write token) for forks using a head.repo.full_name check, ensuring the job runs exactly once per PR event.
• pre-commit.yml: Replaces pre-commit/action with a manual install; uses fetch-depth: 2 so HEAD^1 HEAD resolves against the merge commit's base parent (capturing the full PR diff), null-delimited xargs -0 --no-run-if-empty, and --diff-filter=d to exclude deleted files — addressing all edge cases from prior review.
• .pre-commit-config.yaml: Adds default_install_hook_types, fixes flake8 arg quoting, adds a commit-msg-stage conventional-commit hook for local dev, and pins the org add-license hook at v1.4.3.

Confidence Score: 5/5

Safe to merge — changes are confined to CI configuration files and a copyright year update, with no impact on application code.

All four changed files are CI/tooling configuration. The pre-commit workflow correctly uses the merge-commit HEAD^1 HEAD diff (with fetch-depth: 2) to capture the full PR changeset, handles deletion-only PRs with --no-run-if-empty, and avoids path-splitting with null-delimited xargs. The conventional-pr workflow pull_request / pull_request_target split is implemented correctly, ensuring the job runs exactly once per event and only grants write access for fork PRs. No application logic is touched.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/conventional-pr.yml	New thin-caller workflow; properly gates pull_request vs pull_request_target using head.repo.full_name to avoid duplicate runs and safely grant write access only for fork PRs. Pinned to v1.4.3.
.github/workflows/pre-commit.yml	Replaces pre-commit/action with a manual run; adds fetch-depth: 2 so HEAD^1 resolves to the merge-commit base parent capturing the full PR diff, null-delimited xargs with --no-run-if-empty and --diff-filter=d, and a pre-commit cache step.
.pre-commit-config.yaml	Adds default_install_hook_types, fixes flake8 arg quoting/spacing, adds conventional-pre-commit (commit-msg stage only), and adds the org-wide add-license hook at v1.4.3.
LICENSE	Copyright year updated from 2020 to 2020-2026; no other content changed.

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