someting is not logical in the behaviour of git :
suppose I have a project and a file in it I don't want to include initially in.
so I put this file name in .gitignore
now all is OK when I write "git status" : the file is ignored.
but later I want this one be a part of my project.
I delete in .gitignore the line that named this file.
but now a "git status" command ignore always this file.
what is wrong ?
did I missed something ?
thanks for any answer
Am 06.08.20 um 16:48 schrieb PANEL Christian:
someting is not logical in the behaviour of git :
suppose I have a project and a file in it I don't want to include initially in.
so I put this file name in .gitignore
now all is OK when I write "git status" : the file is ignored.
Like this, right?
$ git init a
Initialized empty Git repository in /tmp/a/.git/
$ cd a
$ echo ignore for now >file
$ echo file >.gitignore
$ git add .gitignore
$ git commit -m initial
[master (root-commit) 2df5d68] initial
1 file changed, 1 insertion(+)
create mode 100644 .gitignore
$ git status
On branch master
nothing to commit, working tree clean
but later I want this one be a part of my project.
I delete in .gitignore the line that named this file.
but now a "git status" command ignore always this file.
what is wrong ?
did I missed something ?
This seems to work as expected for me (continued from above):
$ >.gitignore
$ git status
On branch master
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: .gitignore
Untracked files:
(use "git add <file>..." to include in what will be committed)
file
no changes added to commit (use "git add" and/or "git commit -a")
So "file" is no longer ignored. Committing the .gitignore change
doesn't change that:
$ git add .gitignore
$ git commit -m 2nd
[master d4c95a1] 2nd
1 file changed, 1 deletion(-)
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
file
nothing added to commit but untracked files present (use "git add" to track)
Which steps did you take to arrive at a different result?
René
On Thu, Aug 06, 2020 at 10:23:54PM +0200, René Scharfe wrote:
So "file" is no longer ignored. Committing the .gitignore change
doesn't change that:
$ git add .gitignore
$ git commit -m 2nd
[master d4c95a1] 2nd
1 file changed, 1 deletion(-)
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
file
nothing added to commit but untracked files present (use "git add" to track)
Which steps did you take to arrive at a different result?
Perhaps also:
git check-ignore -v file
would be helpful for seeing why Git thinks it might be ignored (e.g.,
another wildcard rule that happens to match it).
-Peff
Am 07.08.20 um 02:02 schrieb Jeff King:
On Thu, Aug 06, 2020 at 10:23:54PM +0200, René Scharfe wrote:
quoted
So "file" is no longer ignored. Committing the .gitignore change
doesn't change that:
$ git add .gitignore
$ git commit -m 2nd
[master d4c95a1] 2nd
1 file changed, 1 deletion(-)
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
file
nothing added to commit but untracked files present (use "git add" to track)
Which steps did you take to arrive at a different result?
Perhaps also:
git check-ignore -v file
would be helpful for seeing why Git thinks it might be ignored (e.g.,
another wildcard rule that happens to match it).
Right. And there is more than one possible place to specify files to be
ignored. E.g. you can use info/exclude in your Git directory (i.e.
.git/info/exclude by default) for repository-specific patterns don't
want to share. See https://git-scm.com/docs/gitignore or the manpage
of gitignore(5) for more details.
René
thanks a lot.
It was exactly what I was seaching (and havent' read yet ;) )
best regards
Le lundi 10 août 2020 à 07:56 +0200, René Scharfe a écrit :
Am 07.08.20 um 02:02 schrieb Jeff King:
quoted
On Thu, Aug 06, 2020 at 10:23:54PM +0200, René Scharfe wrote:
quoted
So "file" is no longer ignored. Committing the .gitignore change
doesn't change that:
$ git add .gitignore
$ git commit -m 2nd
[master d4c95a1] 2nd
1 file changed, 1 deletion(-)
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
file
nothing added to commit but untracked files present (use "git add" to track)
Which steps did you take to arrive at a different result?
Perhaps also:
git check-ignore -v file
would be helpful for seeing why Git thinks it might be ignored (e.g.,
another wildcard rule that happens to match it).
Right. And there is more than one possible place to specify files to be
ignored. E.g. you can use info/exclude in your Git directory (i.e.
.git/info/exclude by default) for repository-specific patterns don't
want to share. See https://git-scm.com/docs/gitignore or the manpage
of gitignore(5) for more details.
René