I would like to start a discussion if no changeset is found, and a note if changeset is present

[utix]

Hi,

I would like to propose a feature about comment type.
With GITLAB_COMMENT_TYPE we can set it to discussion or note.
When a changeset is missing I would like to have a discussion to block merge request without resolution of the discussion.
If one is set a simple note is ok

I propose to add an optional configuration GITLAB_COMMENT_TYPE_IF_MISSING to allow this behaviour.

If it is ok I will create a PR with this modification

[Filipoliko]

We were discussing very similar topic in our company. We wanted to add the necessity to resolve the discussion if changeset is missing, but if the changeset was available, no resolution should be needed.

I think, that maybe a nicer approach about this could be resolving the discussion if changeset file is part of the MR and unresolving it if it is not. There is an exposed API to manipulate the resolution state of a discussion thread.

For more context... we configured our gitlab projects to make unresolved discussions in MR block the merge button. This helped us not to forget about missing changeset files, but became a bit of an annoyance for those who are not forgetting, but still have to resolve the discussion all the time before merge.