I think that is a paraphrase of the suggestion to
git rm --cached settings
echo settings >> .gitignore
when changes to a file 'settings' that was already tracked (and often
contains user-specific settings) should be ignored. This misguided and
short-sighted "solution" is repeated numerous times on Stackoverflow.
Not something that we should encourage.
So what should be done in this scenario? And why is it a discouraged and
misguided thing?
On 1/15/22 14:33, Johannes Sixt wrote:
Am 15.01.22 um 06:17 schrieb Elijah Newren:
On Fri, Jan 14, 2022 at 3:03 PM Jaydeep Das <jaydeepjd.8914@xxxxxxxxx> wrote:
and other parameters like `--force`
could be added which would delete that file cache if that
file was already committed.
I don't understand what you mean by this.
I think that is a paraphrase of the suggestion to
git rm --cached settings
echo settings >> .gitignore
when changes to a file 'settings' that was already tracked (and often
contains user-specific settings) should be ignored. This misguided and
short-sighted "solution" is repeated numerous times on Stackoverflow.
Not something that we should encourage.
-- Hannes
