Skip to content

Conversation

@assignUser
Copy link
Member

@assignUser assignUser commented Jan 7, 2023

@github-actions
Copy link

github-actions bot commented Jan 7, 2023

@github-actions
Copy link

github-actions bot commented Jan 7, 2023

⚠️ GitHub issue #15249 has been automatically assigned in GitHub to PR creator.

@cyb70289 cyb70289 merged commit 33d677c into apache:master Jan 10, 2023
@assignUser assignUser deleted the add-pr-template branch January 10, 2023 03:48
@ursabot
Copy link

ursabot commented Jan 10, 2023

Benchmark runs are scheduled for baseline = 7e02fde and contender = 33d677c. 33d677c is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.23% ⬆️0.03%] test-mac-arm
[Finished ⬇️0.0% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.2% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 33d677c4 ec2-t3-xlarge-us-east-2
[Finished] 33d677c4 test-mac-arm
[Finished] 33d677c4 ursa-i9-9960x
[Finished] 33d677c4 ursa-thinkcentre-m75q
[Finished] 7e02fde6 ec2-t3-xlarge-us-east-2
[Failed] 7e02fde6 test-mac-arm
[Finished] 7e02fde6 ursa-i9-9960x
[Finished] 7e02fde6 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

EpsilonPrime pushed a commit to EpsilonPrime/arrow that referenced this pull request Jan 10, 2023
* Closes: apache#15249

Lead-authored-by: Jacob Wujciak-Jens <[email protected]>
Co-authored-by: David Li <[email protected]>
Signed-off-by: Yibo Cai <[email protected]>
@kevingurney
Copy link
Member

My sincere apologies for not getting a chance to provide feedback on this pull request while it was still open. The pull request template looks great! This should help further lower the barrier to entry for contributions.

Thank you @assignUser for taking the initiative to make this a reality!

@@ -0,0 +1,62 @@
# Which issue does this PR close?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we start to use this, that will get duplicated with the * Closes .. that the bot adds. Do we then want to remove the bot action? (or some way to unify those? but since this is free form, it might be difficult to have the bot check it)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's also an option. As long as we still require an issue and ask it to be in the title, then this is indeed a bit redundant (and we could have a hidden comment explaining that it should be in the title)

-->
Closes #

# Rationale for this change
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seeing some first PRs with this, shall we use a smaller header? (eg ### instead of #)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current header does looks too big IMO.

@jorisvandenbossche
Copy link
Member

While I think it is a good effort to improve the PR template and top posts in PRs, my feeling is that this is at odds with how we currently use the body of the top post for the merged commit message. For example, many people will leave the commented-out help messages (since they are not visible anyway), but they will appear in the commit messages.

Personally, I think we can move the merge script to only use the title of the PR as commit message, and not the body text?

@kevingurney
Copy link
Member

@jorisvandenbossche - that's a great point about the comments being included in the commit message. Personally, I like the new template (especially how the comments help guide contributors on what to write). However, I agree that the merge script including comments in the commit message is not ideal. Could we have the the merge script remove the comments automatically?

Also, I think having the pull request description (as opposed to just the title) in the commit message is preferable because that keeps the rationale for the changes and associated implementation info directly in the Git history for future reference.

@assignUser
Copy link
Member Author

@jorisvandenbossche @kevingurney @cyb70289 please see #33620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Documentation] Add PR template

6 participants