-
Notifications
You must be signed in to change notification settings - Fork 34
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
Review Unified Label/Diary Screen PRs #779
Comments
I created 2 comments on Tyler's PR, which includes commits to do the To-Do for Unified Diary Screen: e-mission/e-mission-phone#870 (comment) e-mission/e-mission-phone#870 (comment) Overall Changes:
Testing:Screen.Recording.2022-08-23.at.10.48.52.PM.mov |
@sebastianbarry did you confirm that all of the comments that I had left on Tyler's changes are now addressed? |
To incorporate your changes, just push them to your repo and create a new PR. the new PR will include all of tyler's commits, listed as authored by Tyler, and your two commits, listed as authored by you. Next steps before I can merge this:
|
I created a new PR containing the changes I made to the Unified diary screen branch: [New] Unified diary screen (adapted from Tyleryandt18's Unified diary screen) e-mission/e-mission-phone#883 The old Unified diary screen is good to be closed: e-mission/e-mission-phone#870 |
Make sure these "changes requested" are all completed. Go through the list: e-mission/e-mission-phone#870 (review) |
Next steps
|
I have gone through the code review changes in the old (Tyler's) PR, and pushed them to my new PR: e-mission/e-mission-phone#883 There are still a handfull of things to go over; any conversation from that old PR code review that doesn't end in Confirmed this change as complete still needs to be addressed. |
This has been merged, tested and just deployed to production. |
Tyler left 2 PRs open relating to the Unified label and Unified Diary screens.
Unified Label screen: e-mission/e-mission-phone#871
To-Do
Unified Diary Screen: e-mission/e-mission-phone#870
To-Do
The text was updated successfully, but these errors were encountered: