threads / discuss / 40535

submodule: allow submodule directory in gitignore

Subject: submodule: allow submodule directory in gitignore

## tl;dr

4 messages between Oct 12, 2015 and Oct 19, 2015.

replies: 3people: 2as markdown or json

Aleksey Komarov· Oct 12, 2015, 06:30 UTC · lore
Hi all!
I'm sorry if the letter came twice. I have troubles with my post client.

I want to organize my repository so its submodules would be located at the root of repository. I'm trying to create .gitignore to ignore all files and don't ignore directories at the same time:

$ cat .gitignore * !*/

Now, I'm trying to add a submodule to my repository, but fail to understand why my .gitignore prevents it from being added. I use the following command to check if my submodule will be ignored or not:

$ git add --dry-run --ignore-missing c/

I have noticed that result of this check is different when directory c/ already exists and when it still doesn't by the time of the check. The described behavior is illustrated by the following example:

$ mkdir git_test $ cd git_test $ git init Initialized empty Git repository in D:/temp/git_test/.git/ $ echo \* >> .gitignore $ echo \!\*\/ >> .gitignore $ git add --dry-run --ignore-missing c/ The following paths are ignored by one of your .gitignore files: c/ Use -f if you really want to add them. $ mkdir c $ git add --dry-run --ignore-missing c/ $

Is this behavior expected? If yes, where can I read about it? Which part of the Git documentation should I consult? How should I correct my .gitignore to pass this check in both cases, when directory c/ exists and when it doesn't?

Aleksey Komarov· Oct 16, 2015, 09:33 UTC · re: Aleksey Komarov · lore

Re: submodule: allow submodule directory in gitignore

On 12.10.2015 13:30, Aleksey Komarov wrote:
Show 5 quoted lines
> Now, I'm trying to add a submodule to my repository, but fail to understand why
> my .gitignore prevents it from being added. I use the following command to check
> if my submodule will be ignored or not:
> 
> $ git add --dry-run --ignore-missing c/

By the way I've just consulted documentation[1]. Can --ignore-missing option be used for checking not already present directories, in addition to ordinary files?

[1] https://git-scm.com/docs/git-add
Jiang Xin· Oct 17, 2015, 12:46 UTC · re: Aleksey Komarov · lore

Re: submodule: allow submodule directory in gitignore

2015-10-12 14:30 GMT+08:00 Aleksey Komarov <leeeeha@gmail.com>:
Show 36 quoted lines
> Hi all!
>
> I'm sorry if the letter came twice. I have troubles with my post client.
>
> I want to organize my repository so its submodules would be located at the root
> of repository. I'm trying to create .gitignore to ignore all files and don't
> ignore directories at the same time:
>
> $ cat .gitignore
> *
> !*/
>
> Now, I'm trying to add a submodule to my repository, but fail to understand why
> my .gitignore prevents it from being added. I use the following command to check
> if my submodule will be ignored or not:
>
> $ git add --dry-run --ignore-missing c/
>
> I have noticed that result of this check is different when directory c/ already
> exists and when it still doesn't by the time of the check.
> The described behavior is illustrated by the following example:
>
> $ mkdir git_test
> $ cd git_test
> $ git init
> Initialized empty Git repository in D:/temp/git_test/.git/
> $ echo \* >> .gitignore
> $ echo \!\*\/ >> .gitignore
> $ git add --dry-run --ignore-missing c/
> The following paths are ignored by one of your .gitignore files:
> c/
> Use -f if you really want to add them.
> $ mkdir c
> $ git add --dry-run --ignore-missing c/
> $
>

To check how an entry (c/) is affected by .gitignore in different cases, you can try this command:

    $ git check-ignore -v c/
Aleksey Komarov· Oct 19, 2015, 02:24 UTC · re: Jiang Xin · lore

Re: submodule: allow submodule directory in gitignore

On 17.10.2015 19:46, Jiang Xin wrote:
Show 42 quoted lines
> 2015-10-12 14:30 GMT+08:00 Aleksey Komarov <leeeeha@gmail.com>:
>> Hi all!
>>
>> I'm sorry if the letter came twice. I have troubles with my post client.
>>
>> I want to organize my repository so its submodules would be located at the root
>> of repository. I'm trying to create .gitignore to ignore all files and don't
>> ignore directories at the same time:
>>
>> $ cat .gitignore
>> *
>> !*/
>>
>> Now, I'm trying to add a submodule to my repository, but fail to understand why
>> my .gitignore prevents it from being added. I use the following command to check
>> if my submodule will be ignored or not:
>>
>> $ git add --dry-run --ignore-missing c/
>>
>> I have noticed that result of this check is different when directory c/ already
>> exists and when it still doesn't by the time of the check.
>> The described behavior is illustrated by the following example:
>>
>> $ mkdir git_test
>> $ cd git_test
>> $ git init
>> Initialized empty Git repository in D:/temp/git_test/.git/
>> $ echo \* >> .gitignore
>> $ echo \!\*\/ >> .gitignore
>> $ git add --dry-run --ignore-missing c/
>> The following paths are ignored by one of your .gitignore files:
>> c/
>> Use -f if you really want to add them.
>> $ mkdir c
>> $ git add --dry-run --ignore-missing c/
>> $
>>
> 
> To check how an entry (c/) is affected by .gitignore in different cases,
> you can try this command:
> 
>     $ git check-ignore -v c/
I try it, but result is the same.

$ rmdir c $ git check-ignore -v c/ .gitignore:1:* c/ $ mkdir c $ git check-ignore -v c/ .gitignore:2:!*/ c/

Behavior depends on whether c/ directory exists beforehand.

← back to recent threads