Confirmed users
1,927
edits
Engineering Workflow/Road Map: Difference between revisions
→Future: WIP: git support
(include revision-stack landings in "Lando for All") |
(→Future: WIP: git support) |
||
| Line 98: | Line 98: | ||
=== cinnabar-less Git(Hub) gecko-dev support === | === cinnabar-less Git(Hub) gecko-dev support === | ||
git-cinnabar was created to allow developers to use Git to interact with Mercurial, mainly [https://hg.mozilla.org]. It has some downsides, however, such as being a bit tricky to install. Ideally developers would be able to use vanilla Git to contribute to Firefox. | |||
If we view Phabricator and Lando as a conduit to getting code into mozilla-central, then ultimately VCS clients would only need to talk to Phabricator. Phabricator natively supports both Mercurial and Git<ref>There is one wrinkle in supporting two VCSes for the same repository: like figuring out parent commits when a different VCS is used to pull down commits; see {{bug|1443375}} for how this was solved with git-cinnabar.</ref> | |||
<references /> | |||
=== Lando headless client API support === | === Lando headless client API support === | ||
=== Lando and Phabricator backout support === | === Lando and Phabricator backout support === | ||
=== Run tests from source directory in local and ci builds === | === Run tests from source directory in local and ci builds === | ||