[CI] PR auto tag

[Boss2002n]

No description provided.

[github-actions]

🏷️ CI Guide

Runs automatically on every PR:

• ✅ Pre-checks (submodule verification, code formatting)
• ✅ Aiter op tests (gfx942 + gfx950)
• ✅ Triton tests on MI35X (only when aiter/ops/triton/** or related paths are changed)

Extended tests (opt-in via labels):

Label	Tests
ci:gfx1250-ffm-triton	Run the five-shard gfx1250 FFM Triton test suite
ci:triton-300x	Run an additional Triton test job on MI300X in PRs; main branch always runs both MI35X and MI300X
ci:sglang	SGLang integration tests: DeepSeek-R1-MXFP4 accuracy, Qwen 3.5 accuracy
ci:atom	ATOM benchmark: DeepSeek-R1-0528, GPT-OSS-120B
ci:atom_full	ATOM accuracy suite for PR and main models from ATOM models_accuracy.json
ci:vllm	vLLM benchmark: GPT-OSS-120B, DeepSeek-R1-0528, Kimi-K2.5
ci:all	All standard extended tests (excludes ci:atom_full)

Only add ci:atom_full for FlyDSL or Triton upgrades.
Add labels via the sidebar or gh pr edit 4737 --add-label <label>

[Copilot]

Pull request overview

Adds automated PR title component tagging via a new GitHub Actions workflow, and documents the behavior in the PR welcome comment to help contributors understand/opt out of the automation.

Changes:

• Introduce a pull_request_target workflow that computes canonical component tags from the PR’s changed files and rewrites the PR title accordingly.
• Update the PR welcome comment to explain automatic title tagging and the no-auto-title opt-out label.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/pr-welcome-comment.yaml	Documents the new PR title tagging behavior and opt-out label in the welcome comment.
.github/workflows/pr-title-tags.yaml	New workflow that derives component tags from changed paths and syncs them into the PR title.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.