Bugzilla

moz-phab version (from `moz-phab --version`): 1.4.3
Python version (from `python3 --version`): 3.9.8
OS: 13.6.1

STR

1. Have a patch that you know is going to not apply cleanly on beta and esr.
2. Have a mozilla-unified repository with central checked out and your patch applied.
3. Run `./moz-phab uplift --train beta`
4. Fix merge issues, and upload patch to phab.

At this stage, you are now based on beta with the altered patch applied to beta.

5. You know it will uplift fine from beta to esr, so run `./moz-phab uplift --train esr115`
6. Accept the uplift request, noting that it says something about changing to planned changes.

Actual Results

The beta uplift created in step 4 has been altered to have the repository set as ESR, in the WIP state and with release-managers as reviewers, e.g. [this revision](https://phabricator.services.mozilla.com/D193039).

Expected Results

The uplift should have created a new revision on phabricator and updated the bug appropriately.

moz-phab version (from `moz-phab --version`): 1.4.3
Python version (from `python3 --version`): 3.9.8
OS: Mac 13.6.1

STR

1. Have a patch that you know is going to not apply cleanly on beta and esr.
2. Have a mozilla-unified repository with central checked out and your patch applied.
3. Run `./moz-phab uplift --train beta`
4. Fix merge issues, and upload patch to phab.

At this stage, you are now based on beta with the altered patch applied to beta.

5. You know it will uplift fine from beta to esr, so run `./moz-phab uplift --train esr115`
6. Accept the uplift request, noting that it says something about changing to planned changes.

Actual Results

The beta uplift created in step 4 has been altered to have the repository set as ESR, in the WIP state and with release-managers as reviewers, e.g. [this revision](https://phabricator.services.mozilla.com/D193039).

Expected Results

The uplift should have created a new revision on phabricator and updated the bug appropriately.