nchammas commented on code in PR #59174: URL: https://github.com/apache/spark/pull/59174#discussion_r4203952119
########## AGENTS.md: ########## @@ -205,7 +205,7 @@ It lists `master` and the latest major's release branches the commit reached (e. ## Pull Request Workflow -PR title format is `[SPARK-xxxx][COMPONENT] Title`. Draft, WIP, MINOR, and TRIVIAL PRs may omit the JIRA ID. The component tag is derived from the JIRA component name: take the last word and uppercase it (e.g. `Project Infra` → `[INFRA]`, `Spark Core` → `[CORE]`, `Structured Streaming` → `[STREAMING]`, `SQL` → `[SQL]`). +PR title format is `[SPARK-xxxx][COMPONENT] Title`. Draft, WIP, MINOR, and TRIVIAL PRs may omit the JIRA ID. The component tag comes from the `COMPONENTS` registry in `dev/merge_spark_pr.py`, the source of truth: each entry pairs a PR-title tag with its canonical JIRA component name and accepted aliases (e.g. `Documentation` → `[DOC]`, `Pandas API on Spark` → `[PS]`, `SQL` → `[SQL]`). Read that registry to pick the right tag. Review Comment: Right, that appspot site is not official, but the contributing guide _is_ official. So what I'm saying is that the official contributing guide should reflect the latest guidance we want contributors to follow, and agents should just be pointed to that guide rather than have their own agent-specific instructions. I've filed https://github.com/databricks/spark-pr-dashboard/issues/88 to have the old PR review site shut down. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
