Confirmed users
86
edits
| No edit summary |  (Correct moz-phab uplift parameters →Requesting Uplift using moz-phab) | ||
| Line 16: | Line 16: | ||
| # '''Find the patch or series of patches in your local VCS.''' You can ''moz-phab patch'' onto your local machine if need be. | # '''Find the patch or series of patches in your local VCS.''' You can ''moz-phab patch'' onto your local machine if need be. | ||
| # '''Determine which uplift train you want to request an uplift for.''' You can see which trains are available with ''moz-phab uplift --list-trains''. | # '''Determine which uplift train you want to request an uplift for.''' You can see which trains are available with ''moz-phab uplift --list-trains''. | ||
| # '''Run ''moz-phab uplift < | # '''Run ''moz-phab uplift --train <train> <first revision of patches to uplift> <last revision of patches to uplift>''.''' Most of the arguments to ''moz-phab uplift'' are the same as ''moz-phab submit''. This will create new revisions in Phabricator that will be uplifted to the specified train. If ''moz-phab uplift'' is run from mozilla-unified, the stack of patches will be rebased onto the target that will be landed to. For example if you specify ''--train beta'', the patches will be rebased onto the ''beta'' head in your local VCS. If ''moz-phab uplift'' is run from central or another non-unified repo, the commits will be submitted without attempting to rebase them. Note you must use ''moz-phab uplift'', not ''moz-phab sumbit'' or any other unsupported tool to submit uplift requests. | ||
| # '''Open the URL as suggested at the bottom of the output.''' | # '''Open the URL as suggested at the bottom of the output.''' | ||
| # '''Complete the uplift request form. See the section below on how to submit the form.''' | # '''Complete the uplift request form. See the section below on how to submit the form.''' | ||