always kept up with the conventionals in my repos! Also, do you think that the types are enough and you must stick with them or you can standardize them for every project?
So, are these enough? Yes, I guess, because I tried to cover the most and these are the standardized ones as far as my experience, but you may find some extra types depending on the project, but still, it will not be much.
And the next question is- if you should stick with them or standardize them, where I am having a little difficulty in understanding the words stick and standardize, are you meaning renaming the existing types?
Sulagna Ghosh Yep. I was wondering if somehow you cannot (or struggle to) categorize a certain thing that you did in the project.
For example: if I have a React component and I add a stylesheet to it, this will fall under feat. But when I'm going to change some properties inside the styling file, this will fall under fix or refactor?
So I thought that inside your team, you can extend a little bit the description of every type, just to have more defined boundaries for every type, or add more type in order to better categorize your work :)
Simone Aiello That is an excellent point. Often this seems confusing because it is just not about using a type but where to use what type. So, of course, adding some extra examples or some explanation, like you gave in your last answer, can give everyone enough clarity to choose the types and obviously covers some extra lengths.
And really thanks to you for pointing that out, I am going to add some extra examples for better clarity.
Thank you.