One important lesson I learned while working on a larger project was to manage the scope of Git commits more carefully. I already knew that each commit should represent a clear change. However, the challenge was keeping the scope of each change under control as the project became more complex.
I usually committed my changes at the end of each day. Even when several files needed to be committed separately, I was able to organize them into appropriate commits. As the project became larger, however, this became more difficult. At the end of one day, I faced a large set of changes that was very difficult to track.
Version control is not only about recording changes. Keeping a clear record of how a project develops is very important. Large and mixed commits make the history harder to understand. This is especially important in collaborative research, where a clear version history helps others understand and work with the project.
I will continue learning more about Git workflows and commit practices and pay closer attention to the scope of my changes during the project. I will also aim to make smaller and more focused commits when they represent clear changes to the project.