If you're a developer, you probably use the versioning system called Git on a daily basis. The use of this tool is crucial for the development proc...
For further actions, you may consider blocking this person and/or reporting abuse
really nice article! I'm practicing these GIT standards actually, thanks for sharing! 😊
Good one!
This is a great summary! Thank you!!
Good one, Anthony! Thanks for sharing this with us. 🙌
Excellent article! Maintaining standardization in our daily lives is essential 😁
This whole debate is irrelevant, just use whatever you are comfortable with. Using Vim doesnt make you more efficient or productive. You know what makes you quicker and more productive? Knowing how to code...
A really nice article to read, it's worth it
These are great recommendations and resources! Thanks for putting this together!
One addition that we usually add is the commit message should include the work ticket number if you are using a ticketing system. This can be a huge help as it connects the commit to whatever additional details, resources, and conversations are associated with the ticket, and can be really helpful for understanding context when looking at old commits.
Gitflow is something that people barely talk about. Just spam "conventional commits" without showing practical examples is kinda useless.
Really great article, loved how you explained these topics :D
Using Conventional Commits everything in commit title goes in lower-case?
Yes! lower-case and hyphen to separate
Thank you for reply, Anthony :)
A nice feature of the
/separator is that in many UI interfaces will use that to infer a directory structure.Adding to the bit about including Jira issue keys, including them in your commit message will auto-link them in BitBucket (e.g.
git commit -m "Refactor LoginDialog" -m "WTM-305")This is great, I generally try to use these conventions on the projects I'm on—however, I've never heard of the commit type. Personally, I think it's unnecessary and adds more overhead than needed—the subject itself should be enough. If your commits are part of a PR, then the PR title should already be descriptive enough to encapsulate the general category of commits.
Insightful post 🔥 @anthonyvii
Even I used to do conventional commits before but when I realised that few practices can level up you as a Developer, I started using standard commits that made other developers in my team feel overwhelmed.
Remember, you are not alone coding the entire project in any organisation. Maintaining standards in your code helps maintain readability, contextual awareness and effecient collaboration.
I just started to apply them. I am happy to see that I am on the right path. However, I had the feeling that at sometimes it feels limiting. I struggled finding the right words. Could also be me of course..
Thanks a lot...tips are very helpful!
I’ve worked with teams that did this and it slows things down for little value.
Nice and really informative article @anthonyvii !
Hi Anthony Vinicius,
Your tips are very useful
Thanks for sharing
Good and simple. Thanks.
Saving this masterpiece
Thanks!!
I normally use underscore "_" instead of hyphen "-", any wrong with that?
No, those practices are optional, and you don't need to follow each one. If your team doesn't have a defined pattern, you don't need to use a hyphen. Some people say that the practice of using a hyphen makes the subject more readable than using an underscore, but it's optional.
nice one
Thanks!!
Great one
Awesome article!! 🔥 Will start practicing these Git practices.
A very good article, easy to read and understand. Thank you for sharing.
really nice article
Thanks!!
Have learnt a lot from this article. Thank you.
Nice, super thanks. I wish I can read this post when I am student
It's really helpful, even though I've been using Git for years. Regards!
Really great article 🔥
What about avoiding force pushes and
git reflogrecovery for such cases? 🧐This is a useful guide! 🔥
These small things sometimes missed from our day-to-day works, especially for the convention of commit message. Thanks for remind us!
good one
Great info! Thank you :)
Thanks for your recommendations, I'm trying to follow these practices on my projecs!
Thanks for highlighting the importance of Git good practices! Clear commit messages and proper branch management can greatly improve collaboration and kidnapping project organization.
The "Conventional Commits" section doesn't seem to follow the previous "Capitalize the first letter of the subject line"?
indiawalkthrough.com/