Luckily Git has a simple tool to help make this easier: the check-ignore command.
If you’re like me you might have a 30 line ignore file and this can be painful. I could troubleshoot this a bunch of ways, the simplest being deleting lines of my ignore file until the files show up in my unstaged list. gitignore file above some of the binaries in my dependency folders “/lib” wont being added to the repository. I have a folder structure that looks like this: The problem arises when you have actual *.dll files that you need to add to your project as references. This is a pretty common occurrence you want to avoid compiled files making their way into your repository if you can. You’ll notice that the above file excludes all of your binary files. Let’s take a sample (overly aggressive) Visual Studio. The problem you have next is when you add a gitignore rule that’s a little too aggressive and your new project files fail to be picked up by Git, but you’re not quite sure which rule is the cause – this post shows you how you can troubleshoot these issues. gitignore file to your repository you easily make this possible (if you’re using Windows, feel free to take a look at my post on creating these files successfully in Windows). One of the first things you figure out when working with Git is that like other source control providers, you want an easy way to exclude files from ending up on your source control to save yourself uploading items such as binaries and local user files (here’s looking at you Resharper!).
0 kommentar(er)
