Make parent operation persist optional message to image tag store

[afalko]

We support PULL_REQ_MESSAGE, however when you run all the message from the original parent command will be lost.

This is useful if parent's PR message has a change log associated with it that has contextual information that might be interesting for child images.

[justinharringa]

Do you happen to have examples/screenshots that could help here? I'm not sure I completely understand the problem statement. Are we saying that all does not post a contextual description?

[afalko]

@justinharringa : all will post whatever you provide in -m xyz. Today it has no way to post what a previous parent -m abc might have done or desired to have done.

[justinharringa]

It closes that old PR and opens a new one with the new message, correct?

…

On Thu, Feb 3, 2022 at 12:17 PM Andrey Falko ***@***.***> wrote: @justinharringa <https://github.com/justinharringa> : all will post whatever you provide in -m xyz. Today it has no way to post what a previous parent -m abc might have done or desired to have done. — Reply to this email directly, view it on GitHub <#302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH6RTQ6Q4FMDRCPTDHCDC3UZLPEPANCNFSM5NPZVDKQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[afalko]

@justinharringa : No PR is opened if you call parent with SKIP_PR_CREATION: https://github.com/salesforce/dockerfile-image-update/blob/master/dockerfile-image-update/src/main/java/com/salesforce/dockerfileimageupdate/subcommands/impl/Parent.java#L49

[justinharringa]

all will close/open new right? 😉