comment-tag doesn’t work anymore

[hanspagel]

We just recently upgraded to thollander/actions-comment-pull-request@v3, since then comments are added again and again and the comment-tag is ignored. 🫨 We’re switching back to v2, but any idea what we’re doing wrong?

Example PR: scalar/scalar#3236
Our GHA workflow: https://github.com/scalar/scalar/blob/main/.github/workflows/ci.yml#L288-L296

[koppor]

Underscore vs. dash issue - the README.md is inconsistent:

---

I would propose to update the README.md to consistently use the new dash (done at #399) - or release a v4 and reverting to underscore.

[nitrocode]

The title of the issue is a little confusing.

Is it that comment_tag input doesn't work anymore and the new input is comment-tag so if the new input is used, the issue is resolved ?

Maybe the old inputs can be added back in but as deprecated ?

inputs:
  comment_tag:
    deprecationMessage: 'This option is removed. Use comment-tag instead.'
  comment-tag:
    description: 'A tag on your comment that will be used to identify a comment in case of replacement.'

https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#inputsinput_iddeprecationmessage

FYI introduced by

• PR feat: manage delete modes in a better way + consistent input naming #391 to close Consistent input naming convention #386

[koppor]

Is it that comment_tag input doesn't work anymore and the new input is comment-tag so if the new input is used, the issue is resolved ?

Yes.

[ViacheslavKudinov]

Hi,
i think all the examples on READMe.md file have to be updated with new input names where is used kebab-case instead of current wrong ones with snake_case.

[thollander]

Hey,

Thanks for the feedbacks. Indeed there was an issue in the refactoring around logs and documentation.
Fixed in v3.0.1 and also on v3 (pointing to v3.0.1) ✅