peter-evans / commit-comment Goto Github PK

This is not really an "issue" of this project but today I just noticed that Github officially removed commit comment from the PR timeline.
https://github.blog/changelog/2022-08-04-commit-comments-no-longer-appear-in-the-pull-request-timeline/

timeline display was useful because I have been using this to generate and display the build/deploy info per commit.
While this is not a real issue of this project, I thought I'd share.
Please feel free to close this.

I am looking for a functionality similar to https://github.com/peter-evans/create-or-update-comment where it allows to update existing comments

The goal is to prevent duplicates when the builds are retried

I have a similar issue as described peter-evans/create-or-update-comment#234 (comment)

Is it possible that this action also accepts body-path as an input

Im using the PR comment for the TF plan

And then im using the commit comment for the TF apply, this makes the apply even longer than the plan and it would be great if I could also pass it as a file, that was truncated if it goes to large

Hi, I recently opened this help request in the comunity section, they told me I should probably have asked here so here I am.
Would you mind reading this and eventually tell me if something like that is possible?

TLDR: i would like to have a variable (output of a command i run in a job) in the body of the comments, is it possible?

Thanks in advance

Is there an easy way to make this comment on the PR itself, not any of the commits in it?

While omitting the sha action input just works for regular commits on branches, these comments are not visible when the action is run for pull requests.

The reason is that for pull requests, actions are run on "merge commits", as you explained here and also documented elsewhere.

By using

            -   uses: peter-evans/commit-comment@v1
                with:
                    body: "I'm sorry Dave, I'm afraid I can't do that."
                    sha: ${{ github.head_ref }}

... things seem to work for both PRs and regular commits.

If this makes sense, you might want to add a short notice in the README file?

I saw the other issue (#6) about the same thing but didn't get a working solution.

It would be great to have an option to use output files for comments. Something similar to the 'crrate-issue-from-file' action.