-
Notifications
You must be signed in to change notification settings - Fork 0
Create pull_request_template.md #74
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
base: main
Are you sure you want to change the base?
Conversation
Out of curiosity, |
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
Great start!
TODO: | ||
- [ ] Perform basic functions test on production robot | ||
- [ ] Test PR feature(s) on production robot | ||
- [ ] Perform basic functions test on prototype robot |
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 feel performing tests on two robots is a bit much per PR and slows things down. I think just testing on production robot is fine, and I would be ok risking a regression on the prototype bot to speed things along. I'm a bit on the fence still though.
Issues this may resolve (delete line if none): | ||
|
||
TODO: | ||
- [ ] Perform basic functions test on production robot |
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.
Who is checking the boxes? I would propose the reviewer either does the test themselves (ideal) or watches the developer do the test.
Adds a PR template for consistent structuring and include important TODOs by default