Inline stack navigation into MR description instead of posting a comment

[Armaldio]

The stack navigation is currently added as an automated comment on merge requests, while similar information is already present in the MR description.

This leads to duplicated content and unnecessary noise in the comment thread.

Since the tool already supports scoped updates via start/end markers, maintaining it as a separate comment doesn't feel justified.

Problem

Duplicate information between MR description and automated comment
Comment thread cluttered with non-discussion content

Proposal

Move the stack navigation block directly into the MR description and manage it using dedicated markers (or at least make the behavior configurable ?)

Note

managed by git-gud comment should also be disableable

[mrmans0n]

FWIW You can disable this altogether in the config if you think it’s duplicative or don’t like it.

I thought about adding it to the templates for PRs somehow, but I preferred having it separate for now. Might revisit in the future, we’ll see.

[Armaldio]

Only the part saying it's part of stack XXX is duplicated.
I've specifically enabled the feature because I wanted to, but it feels weird having info in two places 🤷