-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add pull request template for PlaceCal #2630
Add pull request template for PlaceCal #2630
Conversation
Added pull request template for PlaceCal
Hey this is looking great! There's a bunch of things noted down in the linked ticket - do you think any of them are worth pulling through? |
Switched the heading for deployment changes to a checkbox under the checklist regarding what the effect of the changes are. Removed the check for tests since as of now we have test automation that notifies the committer that their changes break existing tests.
@kimadactyl this should be good to go now. Thanks for the review 🙌🏿 |
Did you have a look at the linked ticket and do you think those issues are either represented or not needed? |
I think not needed. The other items could be moved into a separate guide on how to interact with pull requests, both for contributors and reviewers. That's how I've seen it done in other projects. Also can't confirm now but things like Edit: also something like changing to view components is ticket specific so that would be added to the ticket for context to whoever ends up working on the feature. |
OK great, happy to merge then :) |
Ugh #2556 is happening again, so annoying! |
Checklist:
Resolves #2501
Description
Motivation and Context
The PR aims to provide a pull request template that makes it easy for new contributors to the project to provide details regarding what their pull request does. It also helps reviewers easily and quickly understand what the pull request is meant to do and review it with the appropriate context in mind.
Type of change
How Has This Been Tested?
By viewing the resulting markdown file.
How Will This Be Deployed?
N/A
Screenshots
N/A