If you're renaming a directory, you'll do a two stage rename with a temp name.KEEP READING: The Bad Batch Guide: News, Easter Eggs, Reviews, Recaps, Theories and Rumors. Please take care and back up anything you don't understand. You can rename the file in a case-sensitive way and commit the change: git mv -cached name.txt NAME.TXT When we checked them on Mac or Windows the files ended up in merged into one folder, but on Linux they were/are two, so the build fails. Turns out that six months ago one of us introduced another folder with the name dasblog while the original was DasBlog. Here's our themes folder structure as seen on .īut when we clone it on Mac or Windows, we see just one folder. However Windows will silently merge them and see just one. If you do this, you'll be able to end up with two separate entries from git's perspective. If you're not careful, you or someone on your team can create a case sensitive file path in your git index while you're using a case insensitive operating system like Windows or Mac. Since Git 1.5ish there's been a setting git config -global core.ignorecase trueīut you should always be aware of what a setting does before you just set it. By default, Mac uses a case-insensitive file system.Windows has a case-insensitive file system.
The build was working great on Windows and Mac.but failing on Linux.
We wanted individual build pipelines to confirm that DasBlog Core was in fact, cross-platform, so we needed to build, test, and run it on Windows, Linux, and Mac. Shayne was working on getting a DasBlog Core CI/CD (Continuous Integration/Continuous Development) running in Azure DevOps' build system. This is part of a larger cloud re-architecture of and the systems that run this whole site. NET Core cross-platform update of the ASP.NET WebForms-based blogging software that runs this blog) with Mark Downie, the new project manager, and Shayne Boyer.