Review and revise a Label2Prod merge request

What the merge request contains

• A title like fix(SHOP-812): apply a discount code once per order, on a branch like autofix/SHOP-812-1.
• What was wrong, in plain words.
• How it was confirmed: the new test and what it showed before the change.
• The fix: what changed and why.
• Verification: the new test fails before the change and passes after it, and your test suite passes, all checked on a clean copy of the repository.
• Confidence, and a Please check list when there is something worth a closer look.

The new test is always part of the change. The commit carries a verification status, and your own pipeline runs as it does for any merge request.

Approving without reading code

You don’t need to be a developer to approve. Start with What was wrong and Verification: they say in plain words what the problem was, and show that the new test failed before the change and passes after it, with your whole test suite passing on a clean copy. Then check the confidence level and the Please check list.

Reading the confidence level

High means a small, focused change. Medium means the change is larger or touches areas that deserve a careful look; the Please check list says where. When Label2Prod cannot reach either, it opens no merge request and explains why on the Jira issue.

Ask for changes

Comment on the merge request with @autofix followed by what to change:

@autofix keep the old error message for API clients and add a test for it

• Label2Prod picks it up within a couple of minutes, adds a new commit, checks it the same way as the first, and updates the description.
• Ask as many times as you need in the first 24 hours after the merge request opens, until it is merged or closed.
• If you post several requests at once, it acts on the newest one. Keep each instruction under 1,000 characters.

Earlier commits stay in place, so the merge request keeps the history of every change you asked for.

When your pipeline fails

If your pipeline fails on Label2Prod’s change, it makes one repair attempt on its own. After that, ask for changes with @autofix as above.

Merging

Label2Prod never merges. Anyone on your team with merge rights in GitLab approves and merges, and the source branch is deleted when you merge.