Feature/promise check surykatka json
/reviewed-on nexedi/slapos.toolbox!72
-
Developer
Sorry for this commit message. Unfortunately !72 (merged) used pipelines, and after clicking
Apply patch
there, it took message from the merge request, instead of the commit. -
Owner
I think this is how
Apply patch
works, regardless of whether pipelines are used or not. If there's only one commit, when youApply patch
the commit on master will use the merge request description as commit message, not the commit message of the commit.Or did you merge while test is running ? Maybe our
Apply patch
work does not understand this situation: -
Developer
I think this is how
Apply patch
works, regardless of whether pipelines are used or not. If there's only one commit, when youApply patch
the commit on master will use the merge request description as commit message, not the commit message of the commit.Hm... Maybe you're right, I do not have often only one-commit MRs. Can it be changed to by default the commit message, not the MR? Or at least have an option?
-
Owner
There's option to change the commit message when applying patch, but not to "use the commit message"
It's not easy to change, it's some nexedi patches to gitlab ( some time ago we fixed a bug with our patches in gitlab-ce!4 (merged) it's not related but you can see where is this code ). It's not option in gitlab config, the option exist, but in gitlab "enterprise edition". I'm not sure but I think in latest version of gitlab the enterprise edition features were merged in the community edition.