Hi
I understand that there are conventions to writing commit messages (fix, feat, test, chore, etc...). That being said, it seems that those commit messages are intended for projects that are already functional and in the process of being updated/changed.
What is the proper way to write a commit message for something you just started from scratch and are changing/updating that (prior to anything being functional). Since there is no user-facing improvement I imagine nothing is considered a "feat"- so would everything be a "chore," "docs," "fix," or "test" ?
02-02-2022 03:43 AM
@PhumeleleSJose wrote:Hi io games
I understand that there are conventions to writing commit messages (fix, feat, test, chore, etc...). That being said, it seems that those commit messages are intended for projects that are already functional and in the process of being updated/changed.
What is the proper way to write a commit message for something you just started from scratch and are changing/updating that (prior to anything being functional). Since there is no user-facing improvement I imagine nothing is considered a "feat"- so would everything be a "chore," "docs," "fix," or "test" ?
Did you find answer? Looking for same information. Thanks
02-08-2022 01:46 AM - edited 02-08-2022 01:46 AM