gitignore

I make an arbitrary change to a file within my git working directory. git status does not recognized that the file has changed. git add /path/to/file has no effect. git add -f /path/to/file has no effect. git status /path/to/file shows the file as in the 'changes to be committed' bucket. I removed my .gitignore file, just to be sure. No change to any of the above behaviors. I have done git reset --hard , re-made my change. No change to any of the above behaviors. What could be going on here? Tim Henigan There are two general reasons why Git will ignore a file: gitignore and submodules . To be

I made a Sinatra app, that will be hosted on Heroku, and the source will be up on GitHub. The problem is that i have a file with API keys, that is currently in .gitignore. Is there a way, that I can push my repo to heroku with the key file and exclude the file when pushing to GitHub? Thanks in advance! It is possible to maintain a separate branch just for deployment, but it takes much discipline to maintain it properly: Add a commit to a production branch that adds the config file ( git add -f to bybass your excludes). To update your production branch, merge other branches (e.g. master ) into

I'm trying to remove a previously tracked directory from git, which works, but it's being added back with each subsequent git add . , git add -A , etc. Here's what I've done: Add to .gitignore in root of project: node_modules Run the following: git rm -r --cached node_modules git commit -a -m "removed node_modules" git push origin master So far so good, this removes the directory from the remote repository. The problem is when I later run git status it tells me the node_modules directory is untracked and keeps adding it back on future commits. What am I missing and/or how do I find the root of

How to I add something to the .gitignore so that the match is not recursive? For example, I wish to ignore the directory foo and the file bar.txt in the current directory, but not any that exist in subdirectories. I have tried this for my .gitignore file: foo/ bar.txt But unfortunately git applies this recursively, so that otherdir/bar.txt and otherdir/foo/ also get ignored, which is not what I want. (Is there a command in git that shows me all ignored files, and reference the .gitignore file that is responsible for the file being ignored? This would be useful for debugging.) The solution is

This question already has an answer here: Do I commit the package-lock.json file created by npm 5? 10 answers To lock the versions of dependencies that are installed over a project, the command npm install creates a file called package-lock.json . This was made since Node.js v8.0.0 and npm v5.0.0 , as several of you might know. Despite of Node.js and npm recommendations about committing this file, several concerns regarding when you should avoid to do it, are also an option. Typically we commit in our projects, nevertheless, it is a peculiar question. While we should commit the package-lock

If I put a pattern in a .gitignore file with a leading slash, does the slash refer to the directory in which the .gitignore file is located, or does it refer to the root of the whole repository? (The man pages I have found have hidden this information carefully.) This is the documentation text : A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c". These are my guesses: If you use an in-repository- .gitignore , the directory in which the .gitignore is located - it is not really useful to make it relative to the repository