Mysterious history with git

In the evening sat down to write a small website for the course work of each other.
Wrote on ROR, create a blank application commits.
7 hours later when the basic functionality was ready,
git commit-a-m "Add some features" git push
git clone
Already on the production server. And wound up almost immediately, the entire application was unharmed kloniroval the server, but I needed something fixed, I made the necessary changes and
git commit-a-m "Tiny fix"
Here is when the problems started, the last thing I remember that I actually was in the first commit, git as Bud would ignore the new files, and committing their changes only in existing ones.
October 3rd 19 at 03:42
1 answer
October 3rd 19 at 03:44
The-a flag to the commit command does not add new files, only modified and deleted.
Do git add for new files
Thank you.
Suspected something like that...
But then I was able to clone from github on the server? - Norene_Hirthe commented on October 3rd 19 at 03:47
There files were already in the Gita, he already tracked so -a worked
The question is how you added them there) - Delpha_Cummin commented on October 3rd 19 at 03:50
In they still there? - Norene_Hirthe commented on October 3rd 19 at 03:53
git clone took the files that have already been added, nothing strange here.
The last question I did not understand. - Delpha_Cummin commented on October 3rd 19 at 03:56

Find more questions by tags GitRuby on RailsGitHub