Jan Klass

How do you handle a case like this? Will Git history be rewritten and force pushed? Or do you have a different workflow/approach?

/spend 35min Ping logic is so complex code /o\

> > Our `scripts/generate_changelog.py` script `pr_number_pattern` already supports PR numbers in the form `(#)`. [1](https://github.com/mumble-voip/mumble/blob/56f03e8d7e5f9cf9d1a318d3a1858db4e09c06ab/scripts/generate_changelog.py#L22-L24) > > It looks like it does, but it does not. The problem was that...

@Krzmbrzl @davidebeatrici Are you fine with this change? Merge commits would no longer be `Merge PR #123: TYPE(scope): Title` but `TYPE(scope): Title (#123)`. Once approved and merged, I would/will change...

> I would prefer having an explicit `Merge` appear in merge commits as they behave very differently during e.g. rebasing and I would like to know if I'll get issues...

Given there's been no solution suggestion to Krzmbrzls concern nor discussion I'll close this as unresolved/unresolvable. I guess we'll continue with no guideline or documented intention then.

Do you have a suggestion how to technically solve this? Does Ubuntu, or better yet a GNU/Linux service provide this functionality?

> By the way, I was always using whatever GitHub pre-populated the text area with. I have no strong feelings on how to format merge commits one way or the...

@DGMurdockIII Unfortunately, Mumbles UI is not implemented in Qt Quick, which is a completely separate UI framework.

To the one described above? If you’re talking about the currently implemented one, this ticket is the wrong place for your question.