# git commit -a -m is not working

4 messages from 2015-09-26 to 2015-09-28. Participants: Alex Radulescu, brian m. carlson, Jonathan Nieder.
Thread: https://gitlist.dev/t/40434

## Alex Radulescu, 2015-09-26 18:51

Subject: git commit -a -m is not working
Message-ID: <CAMWrOy7YoAofbzfW+dy=v1TRgWGe5OuZ8U2x+Q-XCKc1y_agRA@mail.gmail.com>
URL: https://gitlist.dev/e/CAMWrOy7YoAofbzfW%2Bdy%3Dv1TRgWGe5OuZ8U2x%2BQ-XCKc1y_agRA%40mail.gmail.com

```
Hi,

This command is not working. Any advice?

Alex:testGit Alex$ git commit -a -m 'made a change'

On branch v1.0

Untracked files:

new_branch.txt

nothing added to commit but untracked files present

```

## brian m. carlson, 2015-09-26 18:54

Subject: Re: git commit -a -m is not working
Message-ID: <20150926185416.GA233088@vauxhall.crustytoothpaste.net>
URL: https://gitlist.dev/e/20150926185416.GA233088%40vauxhall.crustytoothpaste.net
In-Reply-To: <CAMWrOy7YoAofbzfW+dy=v1TRgWGe5OuZ8U2x+Q-XCKc1y_agRA@mail.gmail.com>

```
On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:
> Hi,
> 
> This command is not working. Any advice?
> 
> Alex:testGit Alex$ git commit -a -m 'made a change'
> 
> On branch v1.0
> 
> Untracked files:
> 
> new_branch.txt
> 
> nothing added to commit but untracked files present

git commit -a does not add untracked files.  Such files might be build
by-products or such and you haven't told Git to track them, so it
doesn't.

From git-commit(1):
  -a, --all
      Tell the command to automatically stage files that have been
      modified and deleted, but new files you have not told Git about
      are not affected.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

```

## Jonathan Nieder, 2015-09-28 17:11

Subject: Re: git commit -a -m is not working
Message-ID: <20150928171132.GA11993@google.com>
URL: https://gitlist.dev/e/20150928171132.GA11993%40google.com
In-Reply-To: <20150926185416.GA233088@vauxhall.crustytoothpaste.net>

```
Hi,

brian m. carlson wrote:
> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:

>> Alex:testGit Alex$ git commit -a -m 'made a change'
>>
>> On branch v1.0
>>
>> Untracked files:
>>
>> new_branch.txt
>>
>> nothing added to commit but untracked files present
>
> git commit -a does not add untracked files.  Such files might be build
> by-products or such and you haven't told Git to track them, so it
> doesn't.

You can run "git add -N <files>" to tell Git to start caring about
some new files (e.g., "git add -N ." to track them all).

Alternatively, you can run "git add <files>" to tell Git that the
current content of those files is ready for commit (e.g., "git add ."
before "git status" and "git commit" to commit everything).

More details are at http://jk.gs/gittutorial.html#_making_changes
(also available by running "git help tutorial").

Thanks and hope that helps,
Jonathan

```

## Alex Radulescu, 2015-09-28 23:34

Subject: Re: git commit -a -m is not working
Message-ID: <CAMWrOy72tRz3VQ2WGwe6bUD6UyTxLp71TsVeGThRVJgrtQCM+A@mail.gmail.com>
URL: https://gitlist.dev/e/CAMWrOy72tRz3VQ2WGwe6bUD6UyTxLp71TsVeGThRVJgrtQCM%2BA%40mail.gmail.com
In-Reply-To: <20150928171132.GA11993@google.com>

```
Hi,

Thank you for your quick and precise support.

Can you share with me some best practices in deploying a web project?
I wave one remote repository, many local repositories (each/developer)
and a shared hosting server. What should I do to push quickly all
changes to my shared server?

Alex

2015-09-28 20:11 GMT+03:00 Jonathan Nieder <jrnieder@gmail.com>:
> Hi,
>
> brian m. carlson wrote:
>> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:
>
>>> Alex:testGit Alex$ git commit -a -m 'made a change'
>>>
>>> On branch v1.0
>>>
>>> Untracked files:
>>>
>>> new_branch.txt
>>>
>>> nothing added to commit but untracked files present
>>
>> git commit -a does not add untracked files.  Such files might be build
>> by-products or such and you haven't told Git to track them, so it
>> doesn't.
>
> You can run "git add -N <files>" to tell Git to start caring about
> some new files (e.g., "git add -N ." to track them all).
>
> Alternatively, you can run "git add <files>" to tell Git that the
> current content of those files is ready for commit (e.g., "git add ."
> before "git status" and "git commit" to commit everything).
>
> More details are at http://jk.gs/gittutorial.html#_making_changes
> (also available by running "git help tutorial").
>
> Thanks and hope that helps,
> Jonathan

```