Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create PULL_REQUEST_TEMPLATE.md #4

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

DaleRitchie
Copy link
Member

@DaleRitchie DaleRitchie commented Aug 31, 2023

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Using Pull Request templates in GitHub can help you write better PRs and make the review process smoother for your team. They provide a standard structure for your PRs and ensure that all necessary information is included.

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates

Related Tickets & Documents

  • Related Issue #

Added/updated tests?

  • Yes
  • No, and this is why: Policy changes unable to be tested at this stage
  • I need help with writing tests

[optional] Are there any post Release tasks we need to perform?

@DaleRitchie DaleRitchie marked this pull request as ready for review August 31, 2023 04:17
Comment on lines +1 to +13
<!--
For Work In Progress Pull Requests, please use the Draft PR feature,
see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.

For a timely review/response, please avoid force-pushing additional
commits if your PR already received reviews or comments.

Before submitting a Pull Request, please ensure you've done the following:
- 👷‍♀️ Create small PRs. In most cases this will be possible.
- ✅ Provide tests for your changes.
- 📝 Use descriptive commit messages.
- 📗 Update any related documentation and include any relevant screenshots.
-->
Copy link
Member

Choose a reason for hiding this comment

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

Can we re-think where this goes? I find it a bit cumbersome to move past to get to updating the bit of the template I need to update.

Copy link
Member Author

Choose a reason for hiding this comment

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

I would really like to leave this at the top as it only appears while editing.

@darren-rdy
Copy link

Is the merge type (squash, merge, etc) part of the template?

Can we have a section for the PR creator to specifically ask questions?

Copy link
Member

@davidkeaveny davidkeaveny left a comment

Choose a reason for hiding this comment

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

Any chance that we could move the first section (What type of PR is this?) below the description? When I see a PR appear in a Slack channel, it's all I really see of the PR - it's just an unnecessary distraction to the content of what is being reviewed.

@davidkeaveny
Copy link
Member

Is the merge type (squash, merge, etc) part of the template?

Can we have a section for the PR creator to specifically ask questions?

Do we really need a specific section for that? If the PR creator wants a discussion, they can add questions, even use the Discussions section for the repository, add comments below etc.

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

Successfully merging this pull request may close these issues.

5 participants