1000 will be empty. |
1000 will be empty. |
1001 In addition, the reason for the transaction opening will be in |
1001 In addition, the reason for the transaction opening will be in |
1002 ``$HG_TXNNAME``, and a unique identifier for the transaction will be in |
1002 ``$HG_TXNNAME``, and a unique identifier for the transaction will be in |
1003 ``HG_TXNID``. |
1003 ``HG_TXNID``. |
1004 |
1004 |
|
1005 ``pretxnclose-phase`` |
|
1006 Run right before a phase change is actually finalized. Any repository change |
|
1007 will be visible to the hook program. This lets you validate the transaction |
|
1008 content or change it. Exit status 0 allows the commit to proceed. A non-zero |
|
1009 status will cause the transaction to be rolled back. |
|
1010 The affected node is available in ``$HG_NODE``, the phase in ``$HG_PHASE`` |
|
1011 while the previous ``$HG_OLDPHASE``. In case of new node, ``$HG_OLDPHASE`` |
|
1012 will be empty. In addition, the reason for the transaction opening will be in |
|
1013 ``$HG_TXNNAME``, and a unique identifier for the transaction will be in |
|
1014 ``HG_TXNID``. |
|
1015 |
1005 ``txnclose`` |
1016 ``txnclose`` |
1006 Run after any repository transaction has been committed. At this |
1017 Run after any repository transaction has been committed. At this |
1007 point, the transaction can no longer be rolled back. The hook will run |
1018 point, the transaction can no longer be rolled back. The hook will run |
1008 after the lock is released. See :hg:`help config.hooks.pretxnclose` for |
1019 after the lock is released. See :hg:`help config.hooks.pretxnclose` for |
1009 details about available variables. |
1020 details about available variables. |
1015 about available variables. |
1026 about available variables. |
1016 |
1027 |
1017 ``txnclose-phase`` |
1028 ``txnclose-phase`` |
1018 Run after any phase change has been committed. At this point, the |
1029 Run after any phase change has been committed. At this point, the |
1019 transaction can no longer be rolled back. The hook will run after the lock |
1030 transaction can no longer be rolled back. The hook will run after the lock |
1020 is released. |
1031 is released. See :hg:`help config.hooks.pretxnclose-phase` for details about |
1021 The affected node is available in ``$HG_NODE``, the new phase will be |
1032 available variables. |
1022 available in ``$HG_PHASE`` while the previous phase will be available in |
|
1023 ``$HG_OLDPHASE``. In case of new node, ``$HG_OLDPHASE`` will be empty. In |
|
1024 addition, the reason for the transaction opening will be in ``$HG_TXNNAME``, |
|
1025 and a unique identifier for the transaction will be in ``HG_TXNID``. |
|
1026 |
1033 |
1027 ``txnabort`` |
1034 ``txnabort`` |
1028 Run when a transaction is aborted. See :hg:`help config.hooks.pretxnclose` |
1035 Run when a transaction is aborted. See :hg:`help config.hooks.pretxnclose` |
1029 for details about available variables. |
1036 for details about available variables. |
1030 |
1037 |