I have a Git repository that I'm using via Azure DevOps, to which I copied a hierarchy of folders and files. Some of these folders only contain another folder. For example:
content
- epm
- bin (this contains files)
- xin (this contains files)
- edc
- bin (this contains files)
What Git is automatically doing is combining the edc and bin folders into edc\bin in the files tree. I even tried manually creating the edc folder with a placeholder file, then the bin folder under that with a placeholder file, then deleting the placeholder file under edc... As soon as I did that, it combined edc and bin back into edc\bin.
The problem with this is that this seems to be an issue when building this via a YAML pipeline into a NuGet package. I use a powershell script that generates the .nuspec file and adds the content to be included. This works fine, where it specifies each separate folder and each file within those folders. So one of the entries it adds is ...content\edc. But then in the NuGet Pack step, which packs the .nuspec, it fails, with the error that it cannot find ...content\edc. Just because of the fact that in the repo's file tree, there is no ...content\edc - only ...content\edc\bin.
Is there a way to stop the auto-combining of folders that only contain one folder like that? If not, where can I submit an issue/request for this to be changed?
I do not want to try changing the folder structure or adding extra things, because these are files that are already used in various projects of ours and I'm turning it into a Git repo and NuGet package for better management and don't want to break existing functionality.