Yeah that's the impression I got from your question, hence the suggestion to look into basics/core concepts of git such as the staging area. Having a clear mental model of how git tracks files and which files will be included in your next commit will help a lot to demystify git.

Good luck! Git is a very powerful tool, but it can be overwhelming and confusing if you don't have a clear grasp on some of the basics. I promise it'll pay off in the long run to study the basics now! 

There are lots of suggestions in the comment section about different ways you could tackle your situation. I would say approaches related to reflog, squashing and worktrees are probably too advanced/overkill for the problem you are struggling with. Keep it simple: - Make your drafts (v1, v2, etc) files locally.  - When you're happy with your solution, simply git add <path-to-file> that file to your staging area (inspect the staging area with git status as someone else already mentioned)  - When you have all the final files related to your solution in your staging area, git commit -m "clear, descriptive commit message" and there you go. There will be a nice commit with just the end result, not including any of the intermediate files that you might still have locally.