Mysterious history with git

Question

git

Hello.
In the evening I sat down to write a small site for a friend's term paper.
Wrote on ROR, created an empty application, committed it.
After 7 hours, when the main functionality was ready,
git commit -a -m "Add some features" git push
Then
git сlone [email protected]:Grindel/churchill.git
Already on the working server. And everything started up almost immediately, the whole application was cloned to the server, but I needed to fix something, I made the necessary changes and
git commit -a -m "Tiny fix"
that's where the problems started, the last thing I remember is that I actually ended up on the first commit, git as-bud- It would ignore new files and only commit changes to existing ones.

Answer 1

The -a flag of the commit command does not add new files, only modified and deleted ones.
Do a git add for new files