moz-phab should be able to submit without updating the working directory
Categories
(Conduit :: moz-phab, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: glob, Assigned: shtrom)
References
(Blocks 1 open bug)
Details
(Keywords: conduit-triaged)
Attachments
(11 files, 2 obsolete files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
moz-phab should be able to submit without updating the working directory.
This will make submission much faster on large repositories such as mozilla-central.
Comment 2•3 years ago
|
||
Found a workaround for me:
- create a temporary branch for the commit to upload.
git branch -c tmp - go into a different directory created with
git-worktreeand switch to the branchgit switch tmp - upload the patches in the other worktree with
moz-phab
The files original worktree doesn't get touched and rebuild times stay low :)
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Propagate this to gitcommand.output and git.git_out.
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Comment 5•1 year ago
|
||
This allows to tailor the output of _get_commits_info for the purpose of
the caller.
Also, fix incorrect typehints for start and end.
| Assignee | ||
Comment 6•1 year ago
|
||
This is probably a noop, but is good for consistency and may come in
handy if we want to change the order in which tests run.
| Assignee | ||
Comment 7•1 year ago
|
||
| Assignee | ||
Comment 8•1 year ago
|
||
Signed-off-by: Olivier Mehani <omehani@mozilla.com>
| Assignee | ||
Comment 9•1 year ago
|
||
This gives us a centralised way to rebuild the full commit message, should it be needed.
| Assignee | ||
Comment 10•1 year ago
|
||
| Assignee | ||
Comment 11•1 year ago
|
||
| Assignee | ||
Comment 12•1 year ago
|
||
The repo implementations do the checkouts as needed.
We still need to checkout the latest commit to be on the correct branch,
but this should be a noop.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 13•1 year ago
|
||
This message format is specific for submission, and we don't necessarily
want it to be used more widely as a commit message.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 14•1 year ago
|
||
This step was removed from the main submit logic, as it was no longer
needed by git, and looked unecessary for hg. Not so!
When computing the diffs, the Hg logic seems to take into account the
current state of the working directory. This leads to incorrect diffs
for anything but the last commit of a stack.
Comment 15•1 year ago
|
||
Comment on attachment 9433216 [details]
mercurial: checkout target commit before get_diff (Bug 1669295) r?sheehan
Revision D226848 was moved to bug 1926924. Setting attachment 9433216 [details] to obsolete.
| Assignee | ||
Comment 16•1 year ago
|
||
Comment 17•1 year ago
|
||
Comment on attachment 9433240 [details]
test_integration_hg: add regression test for diff generation without checkout (Bug 1669295) r?sheehan
Revision D226862 was moved to bug 1926924. Setting attachment 9433240 [details] to obsolete.
Description
•