You can mention whatever you want in a resume, but talking about the number of commits is not going to necessarily be helpful. Contribution to a project does not necessarily correspond to number of commits.
For example, one person may write relatively small chunks of easy code, and commit each time they finish one. Another person may write large chunks of highly complex and important code, and write several parts before committing. The first person may have more commits but not make a bigger contribution to the project. As an extreme example, a person who every time they make a commit breaks the build, has to undo it, fix it and commit again has three times as many commits as another person who gets it right each time; you wouldn't say they were better than the other person though.
I recommend focussing on the functionality of the code you wrote. Write down what parts of the project you wrote, and what they contributed to the end result. it will be much better.