"<No comment>" comment is translated to "<No comment to"

[jacobilsoe]

It seems that > -> --> are all replaced with to when translating the commit message from Rtc to Git. Is this really necessary? I don't see why > should be disallowed in a git commit message.

[ohumbel]

This is due to method replacegitcreatingfilesymbol in gitFunctions.py.
I think it has to do with the way we execute git commands on the command line.
Maybe @WtfJoke remembers the details?

[WtfJoke]

@ohumbel is correct.

I barely remembered. However after some testing and viewing the commits I think I was able to...

If you dont quote the git commit message and it contains ">", git will create a file...

Example:
"git commit -m Fixed some details -> please check User Story 3133"
This will create a file named "please"

Probably its not necessary anymore because I quote the message on commit.
What worries me a bit is that during the time I implemented it, I woted the commit-message already (see 24ae5e6). So there shouldnt be an issue....

I am going to write some tests...

[WtfJoke]

Tests were positive. It looks like it was more a precaution thing. I removed it now.
But would be glad if one of you guys ( @ohumbel / @jacobilsoe ) could test if there are no files get created in the root directory of the migration.

I will close this issue after I got feedback from one of you guys.

EDIT: Damn... Im also anyAuthor :/

[jacobilsoe]

The comments in my migration run looks correct now. Thanks.

[WtfJoke]

Thanks you, for your feedback. I guess no files has been created by the git commands. Therefore close