You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workflow runs again, deletes the comment with tag foo
Current functionality
Workflow runs, creating a comment with tag foo
Workflow runs again, deletes the comment with tag foo
New comment is created in deletion step
a. Ideally, you would not have to create a new comment upon deletion of another comment
Here's an example workflow snippet
- name: Post Commentuses: thollander/actions-comment-pull-request@v2with:
message: | #### hello worldcomment_tag: foomode: recreate
- name: Delete Commentuses: thollander/actions-comment-pull-request@v2with:
message: | #### Why do I need this to delete?comment_tag: foomode: deletecreate_if_not_exists: false # thought this may fix it (it does not :/)
At the end of this, the Post Comment comment is deleted, but seemingly always replaced with a new comment that has the contents of the message in the Delete Comment step.
Ideally, there would be a way to delete an existing comment without creating a new one.
If there is a way to do this and I'm missing something here, please let me know
The downside still with this approach is that if you have notifications setup to pipe into your company chat like Slack you will get notifications for these placeholder message which get deleted which is a bit confusing
Desired functionality:
foo
foo
Current functionality
foo
foo
a. Ideally, you would not have to create a new comment upon deletion of another comment
Here's an example workflow snippet
At the end of this, the
Post Comment
comment is deleted, but seemingly always replaced with a new comment that has the contents of the message in theDelete Comment
step.Ideally, there would be a way to delete an existing comment without creating a new one.
If there is a way to do this and I'm missing something here, please let me know
Thanks!
Update: seems this functionality may not be supported by GitHub: https://github.com/orgs/community/discussions/26256
The text was updated successfully, but these errors were encountered: