PublishUprevChanges should include the final git sha1 in its logged output |
||
Issue descriptionsimilar to bug 671766 , we should include the final git details when pushing commits so we can more easily coordinate git sha1's across logs/repos
,
Mar 10 2018
This bug has not been touched in over a year. It is probably no longer relevant. |
||
►
Sign in to add a comment |
||
Comment 1 by autumn@chromium.org
, Dec 7 2016