-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore: update pull_request_template #3033
Conversation
.github/pull_request_template.md
Outdated
- [ ] I have tested those changes | ||
- [ ] I have added tests (skip if just adding/editing providers) | ||
|
||
<!-- Testing instructions (if applicable) --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
arguably we could get rid of this one but @nalanj raised a good point where we often make the assumption that the reviewers have all the context to tests the PR.
## Checklist before requesting a review (skip if just adding/editing APIs & templates) | ||
- [ ] I added tests, otherwise the reason is: | ||
- [ ] I added observability, otherwise the reason is: | ||
- [ ] I added analytics, otherwise the reason is: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, usually I go simpler. Checkboxes are annoying and honestly, after a while, you stop caring.
# 🤓 Context
# 🧪 How to tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would go for that if it was a private repo but since it is public I would be slightly more verbose
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I agree with Samuel, after a while you stop caring for the checkboxes.
nobody likes checkboxes apparently so let's get rid of them: 9a62043 |
9a62043
to
e239147
Compare
e239147
to
cc88e8a
Compare
My take: having a checklist of things that rarely applies is pretty useless. I (and I am sure not the only one) just ignore the observability and analytics points. I propose this change to focus on the things that matter: description of the change, testing and ticket All of them almost always applies. Also changing to comments so the template instructions don't show once the PR is submitted
cc88e8a
to
b627882
Compare
My take: having a checklist of things that rarely apply is pretty useless. I (and I am sure not the only one) just always ignore the observability and analytics points. I propose this change to focus on the things that matter: description of the changes, testing and ticket. All of them almost always applies.
Also changing to comments so the template instructions don't show once the PR is submitted
Checklist before requesting a review (skip if just adding/editing APIs & templates)