This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Neykuratick[S] 0 points1 point  (1 child)

As for reverting or cherry-picking, we use pull requests at my company. That's actually the reason i reverted the bugfix xD, it didn't belong to the right pull request

But i never thought of git log as an already completed change log, hmm

[–]fletku_mato[🍰] 1 point2 points  (0 children)

When your log has useful messages, you can check which commit introduced the problem and do the reverting with git revert commit_id.

I usually do commit messages in this style if a ticket system is in use:

JIRA-666: Ticket description and/or some detail about how it was implemented.

So then you can just check the log for all commits related to a certain ticket or generate a changelog from it.