view .gitlab/merge_request_templates/Default.md @ 50096:d41960df197e

dirstate: wrap repository change in appropriate context in `test-context`

We need the `wlock` (to add files), the `lock` (to commit), a `transaction` (to
commit) and a `changing_files` context (to add files).

Strictly speaking, we could let the commit take the `lock` and create a
`transaction`, but it seems more consistent that way.

/assign_reviewer @mercurial.review


<!--

Welcome to the Mercurial Merge Request creation process:

* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.

More details here:

* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod

-->