As we are casual game developpers with professional experience in other IT realms, we need to document our choices in repo interaction, mainly flow and naming conventions, to allow the project expand should it grow, properly.
Questions
What organisation should we adopt for branch naming, creation, merge ?
What conventions for commits ?
Answers
I (Hassim) vote for Git Flow (Link for details) as it is known by many devs,
and Angular naming convention (Link for details) for the same reason.
For file organisation and in-code convention, I vote for Google style
Context
As we are casual game developpers with professional experience in other IT realms, we need to document our choices in repo interaction, mainly flow and naming conventions, to allow the project expand should it grow, properly.
Questions
What organisation should we adopt for branch naming, creation, merge ?
What conventions for commits ?
Answers
I (Hassim) vote for Git Flow (Link for details) as it is known by many devs, and Angular naming convention (Link for details) for the same reason.
For file organisation and in-code convention, I vote for Google style