First, remove the file from the index: git rm --cached dbconfig. Php Then, in the root of the repository, create . Gitignore and add dbconfig.
Php to it. Git add . Gitignore and git commit -m "new gitignore" and it should go missing the next time you do a git status or add .
Where exactly should I run git rm --cached dbconfig. Php? Should it be in the same folder that dbconfig.
Php is in? – perpetual_dream Nov 20 at 16:48 1 You can run it in the root of the project, as long as you specify the path to the file. So you could do git rm --cached path/to/dbconfig.
Php or just change to that directory and run git rm --cached dbconfig. Php – melee Nov 20 at 17:38.
Add a file named . Gitignore in the repository and put a line in it: dbconfig. Php Then git add .
Gitignore and commit it. If you already committed the file before, you might want to reset to back before you committed it and re-add the other files, omitting the one you don't want tracked. (Removing it and committing again would remove it from tracking, but the history would still be there - assuming the file contains sensitive data, you wouldn't want that.) help.github.com/ignore-files.
Use the . Gitignore file. One thing that can catch people out initially is that when you add a file to .
Gitignore you then need to add and commit the . Gitignore file itself and only after that will the file be ignored. You may also find that the graphicals tool gitx(Max) or gitg(Linux) make these changes easier.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.