Re: A new feature command request `cmd_ignore`

From: Elijah Newren <newren@gmail.com>
Date: Jan 15, 2022, 05:17 UTC
Message-ID: <CABPp-BFY2issEqOj1Oj71k=494vc8E563CndxPZfXYrteFoNhw@mail.gmail.com>
In-Reply-To: <11860e44-beff-39e6-2efc-53324223caee@gmail.com>

On Fri, Jan 14, 2022 at 3:03 PM Jaydeep Das <jaydeepjd.8914@gmail.com> wrote:

>
> Generally, To ignore files from a repository, we just have to add the
> file name in `.gitignore`. But this task becomes a bit
> tedious when there are a lot of unstaged files which you want to ignore.

'unstaged' implies the file is tracked (i.e. previously added), but has local changes. I think you mean 'untracked' here.

> `git ignore [file names]`
>
> would add that file to `.gitignore`

If there are lots of untracked files, why is it less tedious to type all of them on the command line, then to type all of them in the .gitignore file? I don't see what effort is being saved.

> 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.