Support multiple editable PR comments: Bug for Monrepos and Matrix Stategy actions

[liqnuks]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

On Github Actions, if we use a matrix strategy to run a preview on PR, with comment-on-pr = true (and edit-pr-comment = true, the default value), for each check, the comment will override the same comment, resulting in at the end of the workflow, we have only one preview result: the last finished run.

Steps to reproduce

On preview workflow:

  preview:
    name: Pulumi - Preview
    runs-on: ubuntu-latest
    strategy:
      matrix:
        app: ["app1", "app2"]
    steps:
[...]
    - uses: pulumi/actions@v3
      with:
        command: preview
        comment-on-pr: true
        work-dir: ${{ matrix.app }}
[...]

Expected:

Have 1 comment on PR, for each matrix value (here, 2)

Actual:

The same comment is updated for each matrix value

Workaround:

Set edit-pr-comment to false, but the PR will be commented for each matrix value and each run of the pipeline... it can be verbose

  preview:
    name: Pulumi - Preview
    runs-on: ubuntu-latest
    strategy:
      matrix:
        app: ["app1", "app2"]
    steps:
[...]
    - uses: pulumi/actions@v3
      with:
        command: preview
        comment-on-pr: true
        edit-pr-comment: false
        work-dir: ${{ matrix.app }}
[...]

[ghost]

I’m having a related problem. I’m also using a matrix, but when I set edit-pr-comment to true the action continues to post new comments (one per job variant) rather than update the existing comments. I’m using 5373458 (because I wanted the “folded” comment body feature).

I’ve tried debugging — I even tried making a fork and adding some debugging — but I can’t figure out why it isn’t working.

Should I open a new issue for my version of this problem?

[RobbieMcKinstry]

@miguel-botelho proposed a good solution in #754
As illustrated by Miguel's point, this is a problem for repos using a monorepo, not use those using the matrix-strategy. I'm going to update the title to reflect that.