This updates the code that prints dependencies to include the (first line of) each change’s summary. It also updates the change-parsing code to accept that output, of course.

This makes it easier, for example, to see that your change has an unintended dependency on another change you haven’t submitted yet.

Example output:

$ cargo run -- change OVTCJNBLEVXDO2B6TKJY2TUSJAR6Z5QUUXCNN5WV7WGH76AD5UOQC
message = 'Show change messages when listing dependencies'
timestamp = '2022-05-13T22:33:42.664757Z'

[[authors]]
key = '3uGTfSxiPfZM9adJMcQLNHqMdb9m3ghhMAxFaFGdAmjJ'

# Dependencies
[2] 5FI6SBEZ6RERERUAIWQJVAY66BEZ7YQOYOUNK2DPOLRGS2X326RAC # Re-implement change printing and parsing
[3] IUH7IMWES3KQTHVWA5UNHAO7QWVCC5PQJ6VLK3RC3T4F2MS74P3AC # Contributor license agreements
[4]+VO5OQW4W2656DIYYRNZ3PO7TQ4JOKQ3GVWE5ALUTYVMX3WMXJOYQC # Removing anyhow in libpijul
[*] VO5OQW4W2656DIYYRNZ3PO7TQ4JOKQ3GVWE5ALUTYVMX3WMXJOYQC # Removing anyhow in libpijul
[*] I24UEJQLCH2SOXA4UHIYWTRDCHSOPU7AFTRUOTX7HZIAV4AZKYEQC # Various post-fire fixes

# Hunks
[...]

Changes can be dependent on the special initial “root add” change which has no message.

Perfect, thanks! And sorry it took so long to review.

I know this is closed, but it would be great if this same thing was printed on the output of the dependents command (https://nest.pijul.com/pijul/pijul/discussions/690 which was closed a few days after this one).