Re: Merge requests

[Bruce Steers <bsteers4@xxxxxxxxx>]

On Fri, 16 Oct 2026 at 18:51, Benoît Minisini <
benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 16/10/2026 à 19:20, Bruce Steers a écrit :
> > nooo, A sad Benoit is a world gone wrong :-\
> >
> > Hope mine are okay, I'm pretty sure I've been doing it right.
> >
> > The last one updating gitlab-ci lacked the usual * NEW: * BUG: type
> > stuff because i looked at your previous commits on the integration file
> > to see you didn't do a proper log. https://gitlab.com/gambas/gambas/-/
> > commit/a9a9b8261a67135764365e84ee159c039c837863 <https://gitlab.com/
> > gambas/gambas/-/commit/a9a9b8261a67135764365e84ee159c039c837863>
> > So I did the same.
> > Please let me know if that was wrong.
> >
> > Respects
> > BruceS
> >
>
> Yes, because changes on GitLab CI (as changes on OBS files) are actually
> not changes on Gambas itself, so they do not go to the changelog.
>
> --
> Benoît Minisini.


Cool , so i guess in that circumstance you do not want the normal syntax or
your automation picks it up as a log?

Also can my additional tweak commits be non-compliant ?

For example i have a merge waiting that shows a list of the class
procedures where you can expand/collapse
The initial commit has correct log syntax
The merge request will have correct syntax

But some additional tweak commits have been done in between that do not
comply.
Is that okay because it is just the merge request that must have the log
syntax?

or must each commit applied to a merge request be correctly formatted?

Cheers for any explanation :)
BruceS