Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
eedrawso1087yI definitely do this too, but it's worse because I make the commit super general because I'm fixing something that should have never been an issue and I'm embarrassed.
-
What would be best practise here? Are there certain tips on how to describe changes and bug fixes?
-
eedrawso1087y@Dollique our project manager is very strict, she wants a short sentence beginning with a capital letter in present tense. Example: Fix bug with this specific thing.
I think it depends between projects and people though, but it's nice to have them consistant. -
@Dollique my team came with few standards of our own. We use tags like bugfix, feature, cleanup, documentation. Each commit is one task item.
Sample:
-Bugfix: security vulnerability in JWT fixed by adding another layer of encryption
Related Rants
Git commits with messages like `bug fixed`, `feature added` etc
undefined
wk47