Menu
There are minor coding style changes that I often want to commit to the source control, but now the change log is full of those changes that do not affect code functionality.
What should I do next time I have to fix minor things like:
595
adjective. If you describe measures or changes as cosmetic, you mean they improve the appearance of a situation or thing but do not change its basic nature, and you are usually implying that they are inadequate.
Cosmetic requirements are nothing but the user interface or just the front end appearance of the software. Most of the times it happens that it keeps changing between different releases. This happens especially in the projects where the agile methodology is being followed.
If you are changing the code file, I don't really see why you wouldn't want to commit and share those changes. If you don't you run the risk that someone else will fix them and then collide with yours.
If they aren't changes that other users want in the codebase, perhaps you should ask yourself why you are spending time writing them.
193
Do commit them, with the commit comment flagged appropriately to make it easier to ignore when skimming through a list of changes.
Don't commit them in the same operation as a change to functionality. That way, if you do break something, it is easier to narrow down what broke it and is easy to revert just the refactoring if necessary.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
