[Dev] How about removing explanation as comment in pull request template?

[kou]

Describe the enhancement requested

The current pull request template: https://raw.githubusercontent.com/apache/arrow/refs/heads/main/.github/pull_request_template.md

For example, the following part is "explanation as comment":

<!--
Thanks for opening a pull request!
If this is your first pull request you can find detailed information on how 
to contribute here:
  * [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
  * [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html)


If this is not a [minor PR](https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes). Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the [Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.) of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

    GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

    MINOR: [${COMPONENT}] ${SUMMARY}

-->

Why?

• They are nuisance when I edit pull request description. (Because most contributors don't remove them.)
• If a committer doesn't use dev/merge_arrow_pr.py, these comments are included in commit message. (Because most contributors don't remove them.)
• I'm not sure whether contributors read them or not...

How about removing them entirely?

### Rationale for this change

### What changes are included in this PR?

### Are these changes tested?

### Are there any user-facing changes?

Or how about keeping them as normal texts not comments and contributors must remove them when they read?

Thanks for opening a pull request!
If this is your first pull request you can find detailed information on how 
to contribute here:
  * [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
  * [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html)

...

### Rationale for this change

...

Component(s)

Developer Tools

[raulcd]

Thanks @kou, this sounds like a good improvement to me 👍

[amoeba]

Prior to this, did we tend to get problematic pull requests? I'm curious why this was added originally. Generally, I'm +1 here though.

[wgtmac]

FTR, it seems that there are 20 commits having the unintentional message.

~/Projects/arrow (main*) » git log | grep "Thanks for opening a pull request" | wc -l
      20

[kou]

How about counting PRs that have auto comment for invalid format PR such as #45487 (comment) ?

https://github.com/apache/arrow/pulls?q=is%3Apr+%22Licensed+to+the+Apache+Software+Foundation%22+%22Thanks+for+opening+a+pull+request%22+ shows 1364 PRs.

[kou]

#15249 is the PR that introduced this pull request template.

[amoeba]

Thanks both of you. I'm +1 as-is but would like to see is retain the links to the contribution guides in the PR if we can. Something like,

Thanks for opening a pull request!

If this is your first pull request you can find detailed information on how to contribute here:

  * [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
  * [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html)

Please remove this line and the above text before creating your pull request.

[kou]

The discussion thread: https://lists.apache.org/thread/7l5ktppo9dfwro6zl10gj6yp5j35sgpb

[singh1203]

Will appreciate to work on it here, post everyone's opinions in the discussion.

[kou]

Based on the discussion, let's choose the idea #45485 (comment) suggested by @amoeba .

[raulcd]

Issue resolved by pull request 45599
#45599

[amoeba]

Thanks @kou