4 ms·
As a rule of thumb: the WHY in the PR, the WHAT in the commits.
by logronoide 4y ago
As a rule of thumb: the WHY in the PR, the WHAT in the commits.
- deleted 4y ago[deleted]
- reacweb 4y agoI would say the opposite. The manager who receives the PR (merge request in gitlab) needs to know what has changed (if it is not obvious from the diff) to assess the change before accepting it. He has to know what has changed, for example to decide which non regression tests to performe. The final user of the software will receive a changelog (a list of commit messages) that shall identify the bugs that have been fixed and the new user requirements that have been added. He needs to know why the code has changed to know what he has to do.