removes the possibility of commit messages having carriage returns
What does this MR do?
Due to web standards all the web forms we had created commit messages with \r\n this MR changes
it so that commit messages can only contain \n.
Before
0000000 M e r g e b r a n c h ' 3 0
0000020 5 3 5 - d i s p l a y - w h e t
0000040 h e r - p a g e s - i s - e n a
0000060 b l e d - i n - t h e - a d m i
0000100 n - d a s h b o a r d ' i n t
0000120 o ' m a s t e r ' \r \n \r \n D i
0000140 s p l a y G i t L a b P a g
0000160 e s s t a t u s i n A d m
0000200 i n D a s h b o a r d \r \n \r \n
0000220 C l o s e s # 3 0 5 3 5 \r \n \r
0000240 \n S e e m e r g e r e q u e
0000260 s t ! 1 1 0 0 7 \n \n
0000273After
0000000 c h a n g e s n a m e \n \n t
0000020 o j e s u a l d o \n \n d i f f
0000040 - - g i t a / R E A D M E .
0000060 m d b / R E A D M E . m d \n i
0000100 n d e x 1 4 1 4 3 c f . . c 7
0000120 e 9 3 f e 1 0 0 6 4 4 \n - - -
0000140 a / R E A D M E . m d \n + + +
0000160 b / R E A D M E . m d \n @ @
0000200 - 1 + 1 @ @ \n - o l a o
0000220 m e u n o m e e m a r i a
0000240 \n + o l a o m e u n o m e
0000260 e j e s u a l d o \n
0000274(Note that they are not the same commits they just serve as an example of the behaviour we are implementing)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #31671 (closed)