threads / discuss / 40434

git commit -a -m is not working

Subject: git commit -a -m is not working

## tl;dr

4 messages between Sep 26, 2015 and Sep 28, 2015.

replies: 3people: 3as markdown or json

Alex Radulescu· Sep 26, 2015, 18:51 UTC · lore
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· Sep 26, 2015, 18:54 UTC · re: Alex Radulescu · lore

Re: git commit -a -m is not working

On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:
Show 13 quoted lines
> 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· Sep 28, 2015, 17:11 UTC · re: brian m. carlson · lore

Re: git commit -a -m is not working

Hi,
brian m. carlson wrote:
> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:
Show 13 quoted lines
>> 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· Sep 28, 2015, 23:34 UTC · re: Jonathan Nieder · lore

Re: git commit -a -m is not working

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>:
Show 31 quoted lines
> 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

← back to recent threads