sapling/edenscm/hgext/pushrebase
Stanislau Hlebik e1e5d4bb0d pushrebase use hookargs correctly if transaction was taken
Summary:
Context: for Mononoke sync job we are considering applying a few pushrebase
bundles under the same transaction to make sync job faster. More details -
https://fburl.com/y4we86hc

Doing two pushrebases under the same transaction seems to fail for  just one
reason - `hookargs` is None on the second bundle. The reason is this line -
https://fburl.com/y4we86hc, after gettransaction() is called
bundleoperation.hookargs is set to None, but transaction.hookargs is set to
current hookargs value.

In this diff pushrebase is changed to check both bundleoperation.hookargs and
transaction.hookargs

Reviewed By: quark-zju

Differential Revision: D14930970

fbshipit-source-id: e4a4dd1c85b1fdca2699dd431040d65f2642ec8a
2019-04-16 03:10:02 -07:00
..
__init__.py pushrebase use hookargs correctly if transaction was taken 2019-04-16 03:10:02 -07:00
common.py pushrebase: fix choosing commit timezone 2019-02-21 00:59:13 -08:00
errors.py codemod: import from the edenscm package 2019-01-29 17:25:32 -08:00
recording.py fix format for broken check-code test 2019-02-22 11:44:51 -08:00
stackpush.py mutation: record predecessors and operation in commit loginfo 2019-04-10 15:16:17 -07:00