This is the primary reason why I am against setting up file structure in the first commit.
We should never have empty files on the master branch, even at the beginning. If it's important for the team to have a common understanding of the file structure, before each file is created, this can be written in the docs.
The likelihood of file and directory names changing is high. Files should only be introduced to the project when they have code in them, as the codebase should increase with each new feature, and never have unnecessary files in it.
This is the primary reason why I am against setting up file structure in the first commit.
We should never have empty files on the
masterbranch, even at the beginning. If it's important for the team to have a common understanding of the file structure, before each file is created, this can be written in the docs.The likelihood of file and directory names changing is high. Files should only be introduced to the project when they have code in them, as the codebase should increase with each new feature, and never have unnecessary files in it.