How can this be manually tested? (brief repro steps)
see original pull requests
What are the relevant TFS items? (list id numbers)
n/a deployment prep
Definition of done:
[x] Title of the pull request is clear and informative
[x] Add pull request hyperlink to relevant TFS items
[x] For large or complex change: schedule an in-person review session
[x] This change has appropriate test coverage
Reminders BEFORE merging
Get at least two approvals
If you're merging from a feature branch into the development branch then "flatten" or "squash" commits
If merging from the development branch into master (or porting changes from upstream) then use github's UI to get review feedback, but use the git command line interface to complete the actual merge.
Reminders AFTER merging
Delete the remote feature branch
Resolve relevant TFS items
(reverse merge) If you merged from the development branch into master then check to see if there are any changes in master that can be merged down to the development branch (like hotfixes, etc). In this case, use github's UI for feedback and the git command line interface for the actual merge.
What does this PR do? Please provide some context
Full merge: dev to Release
Where should the reviewer start?
n/a. all changes have been reviewed individually
How can this be manually tested? (brief repro steps)
see original pull requests
What are the relevant TFS items? (list id numbers)
n/a deployment prep
Definition of done:
Reminders BEFORE merging
Reminders AFTER merging