You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitted By: kevin.beddingfield
Topic: PR Review
Team: Tier 1 Support
Hi! We have a stack of PRs that we'll be looking to review/merge. The work has been split out into chunks including steps like isolating migrations to their own PR. Since there are 11 of them, we're wondering if we should communicate with the review team regarding looking at the set as a single unit of work vs sending all 11 through the process individually relying on standard workflow. Would love the platform team's thoughts on how we should structure for review. Thanks!
Submitted By: kevin.beddingfield
Topic: PR Review
Team: Tier 1 Support
Hi! We have a stack of PRs that we'll be looking to review/merge. The work has been split out into chunks including steps like isolating migrations to their own PR. Since there are 11 of them, we're wondering if we should communicate with the review team regarding looking at the set as a single unit of work vs sending all 11 through the process individually relying on standard workflow. Would love the platform team's thoughts on how we should structure for review. Thanks!
The PRs:
https://github.com/department-of-veterans-affairs/vets-api/pulls/nihil2501
The text was updated successfully, but these errors were encountered: