-
Notifications
You must be signed in to change notification settings - Fork 18
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
New PR template #1248
base: develop
Are you sure you want to change the base?
New PR template #1248
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1248 +/- ##
=======================================
Coverage 12% 12%
=======================================
Files 266 266
Lines 7201 7201
=======================================
Hits 806 806
Misses 6395 6395 |
d2cacc0
to
d91f57f
Compare
# Review Checklist | ||
|
||
- [ ] Writes a summary in `whatsnew/whatsnew-pt-PT` of the new changes | ||
- [ ] Terms and conditions reflect the changes |
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.
Terms and conditions should be updated on every PR, if necessary. The reason is the app will be used by beta testers, which are also subject to the terms and conditions of uni.
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 think it can be a little annoying and pushing the responsibility to the person who made the release and its reviews, will allow taking a preoccupation from each PR
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 agree that it is a bit annoying but, with each PR, we are essentially creating a release (for our beta testers). As such, the terms and conditions need to be kept up-to-date for them. If we remove public access from the beta track, we can push this to the release checklist.
UI/UX Test with diferent text zoom levels |
Add something responsive |
Closes #997
Let's open the debate!!