You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Generated Mule 4 projects on Windows copy the .git directory from the original without marking it as "hidden".
Expected Behavior
If it is expected for the .git directory to be copied, it should share the same attributes as the original. On Windows, this often includes it being hidden as this is the default when using git init or git clone on that platform.
Actual Behavior
The .git directory is copied into the generated Mule 4 application's directory, but it is not marked as "hidden".
Relevant logs
Unfortunately, there are no logs for me to provide; it produces this unexpected output without error.
Reproducible Test Case
This can be done in any project that is version-controlled with Git. I was able to create a single-file project in Mule 3, run git init in its root directory and then run MMA 1.4.0 on it to reproduce the issue.
The text was updated successfully, but these errors were encountered:
Version used
MMA 1.4.0
Describe the bug
Generated Mule 4 projects on Windows copy the
.git
directory from the original without marking it as "hidden".Expected Behavior
If it is expected for the
.git
directory to be copied, it should share the same attributes as the original. On Windows, this often includes it being hidden as this is the default when usinggit init
orgit clone
on that platform.Actual Behavior
The
.git
directory is copied into the generated Mule 4 application's directory, but it is not marked as "hidden".Relevant logs
Unfortunately, there are no logs for me to provide; it produces this unexpected output without error.
Reproducible Test Case
This can be done in any project that is version-controlled with Git. I was able to create a single-file project in Mule 3, run
git init
in its root directory and then run MMA 1.4.0 on it to reproduce the issue.The text was updated successfully, but these errors were encountered: