New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New comment on GitLab #1084
Comments
Yep, I agree, I don't think it was probably added right to the GitLab side looking at it's usage in comparison to GitHub |
Shall I submit the patch then? |
Yep, sure 👍 |
AlexDenisov
added a commit
to AlexDenisov/danger
that referenced
this issue
Feb 22, 2019
Current implementation of GitLab request source does not create a new comment when requested via the `--new-comment` CLI option, but rather updates the old one. This patch fixes the issue by checking whether new comment is requested before updating Pull Request. Preliminary discussion of this issue is here: danger#1084
AlexDenisov
added a commit
to AlexDenisov/danger
that referenced
this issue
Feb 22, 2019
Current implementation of GitLab request source does not create a new comment when requested via the `--new-comment` CLI option, but rather updates the old one. This patch fixes the issue by checking whether new comment is requested before updating Pull Request. Preliminary discussion of this issue is here: danger#1084
AlexDenisov
added a commit
to AlexDenisov/danger
that referenced
this issue
Feb 22, 2019
Current implementation of GitLab request source does not create a new comment when requested via the `--new-comment` CLI option, but rather updates the old one. This patch fixes the issue by checking whether new comment is requested before updating Pull Request. Preliminary discussion of this issue is here: danger#1084
Resolved via #1085 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report
What did you do?
I ask Danger to always create new comments:
What did you expect to happen?
For each re-run of our CI expected to see a new comment, preserving the old one.
I.e., the merge request history should look like this:
What happened instead?
The first comment' body is replaced with a new comment.
I.e., the merge request history looks like this:
And after new commit:
Your Environment
Which CI are you running on?
Jenkins
Are you running the latest version of Danger?
5.14.0
What is your Dangerfile?
Additional info
The fix for my expected behaviour is trivial (see below), but the question is whether it is a bug or I misunderstand the purpose of the
--new-comment
flag?Thank you for the great tool, it helps a lot!
The text was updated successfully, but these errors were encountered: