Hi there,
We are using UiPath Studio 2022.10.4 and store all our projects on gitlab. For version control we use the GIT integration in UiPath Studio.
Recently we have seen some strange behaviour of the version control in Studio. Here is the description to reproduce:
Create a new project and a new sequence. Name the sequence something like “# TEST Sequence.XAML”. Then use a “use application” activity in the new sequence and a “check app state” activity within it.
Now the pen icon tells me that there are new changes in my project. Clicking on it opens a new window with a list of all changed files. In the list I can see that the .screenshots folder has been changed (makes sense), and the new file “# TEST Sequence.XAML” has changes. Well, everything looks good. When I commit and push the changes, the window closes, but the pen tool shows that there are uncommitted changes. After clicking the pen, I see that the XAML has indeed not been committed, and this is also shown in the gitlab repository.
After some testing I found that the culprit was the # symbol. If the filename has a # symbol as the first character, that file somehow gets ignored on the first commit, but not on the second.
Can anyone explain to me how this causes this problem? I do not recall that filenames cannot begin with a # and it works on the second commit.