I think after that we installed another Unity asset package, Odin Inspector. Then we learned that the files are still tracked, so at that point we untracked them and I don’t Recall the exact command line arguments that we used.Īt that point all was good, and here I don’t recall the exact sequence of events. In our inexperience we first gitignored the package folder and its contents. So if that is the case, I think you are telling me is that at some point someone had to untrack these files that are being flagged.Īnd that everyone who uses the command line would see the same untracked flags. I mean, I thought I understood that you can have files in the repo folder that are not tracked but that for that to happen someone would have to explicit untrack a file, an in which case we'd normally also want to gitingore it. does it become tracked or untracked? (I think you are saying it automatically becomes tracked - I thought I also understood that about git and repos) If I create a new file in a project, or drag a file into the project folder. Are you refering to the repo, or the project folder that the repo allows us to share? (I think you mean the repo) When you say "The entire point is that untracked files are not added" I'm not sure what is being added to. Because that, in fact, is not what you want.Sorry for my lack of knowledge and inability to phase the questions properly: But git (and, by extension, GUIs such as GitHub Desktop) won't touch repos in repos, because it assumes that's not what you want. ) in a different git repository.Īny other subfolders (and files) in your parent (that aren't a repository in their own) will be read properly. That also makes sense, since it isn't a good idea to have a full repository (including data, configs. When you now run git in your parent folder, git sees that the subdirectory is a repository in its own and essentially goes "ah, that folder is already controlled by something else" and doesn't touch it. Because now you have a git repo (VS's) in a folder that is in a different git repo (the one you manually created). But, if you want your new project to be a subfolder of a repository, this can cause the exactly the "problem" you've seen. This generally makes sense if you want to source-control your project, that's why that thing is there. When "Use git for version control" is ticked, Visual Studio makes a git repository out of your new project. Let me explain why it is like this, if you wonder in the future. If anyone has struggled and has an answer, that would be great. So then I removed the files and Github will still not read the files within the " Demo" folder or any other folder for me to commit and push and I cannot figure out why. So I tested a theory to see if Github could read files in general, so I copied some files and added to that repo folder, and Github desktop read and recognized the files. I made sure I was in the right repo multiple times. When I open up Github Desktop to commit and push the files back up to the repository, the application will not read the contents of the " Demo" folder itself. Then we have to go into Visual Studio 2022 (not VS Code) and create our C# program, and save it within the repository we cloned. So, for class, I have to clone down the repository from our teacher using Github Desktop, which is all well and easy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |