Update default merge request template to include UX
Problem
In the default merge request template, we have the following checklist item:
I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied frontend, backend and database labels accordingly.
We still have too many cases where designers are not getting pinged on MR reviews, and calling out the UX label in that process might help us already right now, while also setting us up for better tracking and automation.
Solution
We should include UX as part of that list to avoid leaving out designers from the MR review process.
I have considered the impact of this change on the UX, front-end, back-end, and database portions of the system where appropriate and applied UX, frontend, backend and database labels accordingly.