If all goes well, run git commit after to re-commit your files. $ git reset aaeb1de3f39a77af223f55bcabba1c649d3f097fįinally, re-stage your files with git add * and check that the ignored files are no longer staged with git status. Then, run git reset to revert your project back to the older version. You can also consider reverting your project to the initial commit, then re-stage your files and commit again.įirst, you’ll want to run git log, and find the hash (highlighted below) of your initial commit. And are using a interface that allows you to revert to an older commit (such as Git Bash).if you’ve initialised your repository in GitHub or GitHub Desktop) Have an initial commit without your project files (i.e.Haven’t had too many commits for your project.The application used here is GitHub Desktop. gitignore is always set up before the commit in this way, you will never run into this issue. gitignore template that will be automatically set up for you. If you are creating your repository from GitHub or GitHub Desktop, you can also choose a. gitignore is set up before you make any commits. Hence, to avoid this, you’ll want to ensure. gitignore list will NOT ignore files that are already tracked by your repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |