IssueComment Body is too long (maximum is 65536 characters)

[xakraz]

We are using your GitHub action to implement a similar UX that Atlantis does for Terraform 😇

But we face in issue with this error

Error: Validation Failed: {"resource":"IssueComment","code":"unprocessable","field":"data","message":"Body is too long (maximum is 65536 characters)"}

💡 It would be nice to be able to split the comment in multiple ones if the body is too long.
Atlantis does that for very long Terraform plans output

[marocchino]

Finding a proper delimiter for strings exceeding 65536 seems a bit tricky. Please give me some time to think about it. If you have any good ideas, PRs are welcome.

[marocchino]

Personally, I don't think anyone would be able to read such a long comment, so it seems better to handle it as an artifact.

[ShankyJS]

Ups, I created a duplicate issue for this #1408.

I just encountered the same issue; It would be really nice to implement a feature similar to atlantis where the comments get chunked into multiple pieces if it's greater than the max size.

Definitely a +1 on this one.

[dudicoco]

@marocchino how about adding an input to the action - delimiter, the action can than determine if the body is too long and split the comment according to the delimiter.

Example:

    - name: Comment on PR
      uses: marocchino/sticky-pull-request-comment@v2.9.0
      with:
        number: ${{ github.event.pull_request.number }}
        delimiter: ---
        message: |
            first comment
            ---
            second comment
            ---
            third comment

[marocchino]

@dudicoco
Thank you for the comment. Splitting and inserting it is straightforward; however, managing the previous state is challenging. If the number of delimiters has changed and the strategy involves rewriting, it becomes necessary to locate all previously written comments. This, however, would require a full scan of comments for the relevant PR, which could impact running speed and API limits.