![]() I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.The MR is named after the desired squash commit to feed the changelog linked to the current milestone.I have considered the scalability risk based on future predicted growth.I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.Performance, reliability and availability I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.I have tested this MR in all supported browsers or determined that this testing is not needed. ![]() I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.I have made sure that the sonar quality coverage is up to standards.If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR. For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users.List all steps to set up and validate the changes on local environment. How to set up and validate locally (or on alpha) These are strongly recommended to assist reviewers and reduce the time to merge your change. MR Front : pamn_client!492 (merged) ⚠ Keep an up to date checklist based on your icescrum tasks during all the draft phase of the MR to help any other developer who would take the job after you to finish it. In doubt, check the conventional commit doc. □ Give your MR the same name that the desired squash commit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |