This is why:
# git status
On branch master
Changes to be committed:
(use "git rm --cached <file>..." to unstage)
new file: myscript.sh
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
(use "git add <file>..." to include in what will be committed)
Putting .gitignore inside the file itself doesn't negate it's behavior.
Just seems like something that should be built in because a) no one wants
to see this listed as an untracked file and b) no one wants this included
in their actual project repository.
On Mon, Mar 10, 2014 at 4:31 PM, Andy Hardy <a...@hardyfamily.org.uk> wrote:
> On 10/03/2014 21:20, rhugga wrote:
> > So .gitignore is used to hide certain file types which is great. But how
> > do you have it ignore the file itself?
> > I put .gitignore in the file itself and that works but seems more like a
> > work around than as intended.
> Why would you want to ignore .gitignore? Surely, as you add more entries
> to the file you want those changes to be committed and made available to
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.