> This happens *only* if the other developers also have somefile mentioned > in their .gitignore. It will be mentioned, because of I can add/push, wait developers pull, add/push I can do this because I was angry or was fired. So this is my last "surprise" for others )) >> EXPECTED: git should warn about that content will be replaced and do not pull/checkout until we force pull/checkout > > If somefile is *not* mentioned in their .gitignore, the file is not > removed and there is a warning. As you can see the file is not just ignored in my case it is important because added to the repo we can think of some sort of default configuration stored in repo. But added to ignore file because developers do not want to track local changes (every developer has own options when configure local instance of application) it *this very important* to not lose these options while switching between branches or pull from remote. And I do not expect and do not want to get such "surprises" from anyone
