Per DPInt Working Group meeting on 8/25 EST, we'd like to get features/changes spread across Prescient and PRONet collected into one 'main' ampscz branch. From this point, we can better collaborate and improve the code base towards network parity.
I've created a new branch ampscz, branched off of mcardle-features-dashboard (a descendant of runsheet-linking). This contains the additional pages and features that I've built into the frontend.
Branch prescient has this commit regarding NextJS version updates. @baylisscg could you open a PR to merge into ampscz? I'm hoping to exercise our workflow rather than just execute myself.
Branch main has this commit about database pool creation, which I suspect we may want to cherry-pick or merge into the ampscz branch. 'Can't automatically merge' is triggering, so I suspect there will be some reconciling for that merge.
@dheshanm @baylisscg
Per DPInt Working Group meeting on 8/25 EST, we'd like to get features/changes spread across Prescient and PRONet collected into one 'main'
ampsczbranch. From this point, we can better collaborate and improve the code base towards network parity.I've created a new branch
ampscz,branched off ofmcardle-features-dashboard(a descendant ofrunsheet-linking). This contains the additional pages and features that I've built into the frontend.Branch
prescienthas this commit regarding NextJS version updates. @baylisscg could you open a PR to merge intoampscz? I'm hoping to exercise our workflow rather than just execute myself.Branch
mainhas this commit about database pool creation, which I suspect we may want to cherry-pick or merge into theampsczbranch. 'Can't automatically merge' is triggering, so I suspect there will be some reconciling for that merge.@dheshanm @baylisscg