Is your feature request related to a problem
In our organization we run OP5dev/TF-via-PR first on dev, then on stage, and finally on prod at various triggers. This generally works well, but it is slightly difficult to see which env a given plan comment is for.
Describe the solution you'd like
Ideally we'd be able to add arbitrary markdown content to the comment that's left by the action, so we can customize exactly how we want to differentiate them. My initial suggestion would be something like a comment-prefix input that's inserted as the first part of the comment body.
Describe alternatives you've considered
We couldn't come up with any real alternatives. We could stitch something together that goes in and edits the comment after OP5dev/TF-via-PR leaves it - or we could register GitHub Apps with different identities for each env, so the avatar changes - but that all seems overkill compared to allowing body customization in the action.
We might also be missing something. I can see that OP5dev/TF-via-PR internally places a few <!-- placeholder-X --> comments in the body, but doesn't use them for anything. Is the intention that they can be used to customize content somehow?
Additional context
Is your feature request related to a problem
In our organization we run
OP5dev/TF-via-PRfirst ondev, then onstage, and finally onprodat various triggers. This generally works well, but it is slightly difficult to see which env a given plan comment is for.Describe the solution you'd like
Ideally we'd be able to add arbitrary markdown content to the comment that's left by the action, so we can customize exactly how we want to differentiate them. My initial suggestion would be something like a
comment-prefixinput that's inserted as the first part of the comment body.Describe alternatives you've considered
We couldn't come up with any real alternatives. We could stitch something together that goes in and edits the comment after
OP5dev/TF-via-PRleaves it - or we could register GitHub Apps with different identities for each env, so the avatar changes - but that all seems overkill compared to allowing body customization in the action.We might also be missing something. I can see that
OP5dev/TF-via-PRinternally places a few<!-- placeholder-X -->comments in the body, but doesn't use them for anything. Is the intention that they can be used to customize content somehow?Additional context