When replying to a Pull Request (PR) in code review style, are commits imporant?

by ryanwebjackson   Last Updated January 13, 2018 18:03 PM

I recently commented on commits directly, and was told that this is not the correct way to reply to a pull request. The requestor stated that it is not commits that are important but the end result of the files. My argument is that if this is true, why not merge all the commits into one before creating the PR.

My question is then, when are commits important in a PR-style workflow?

I'm aware this might be opinion-based, or Web Apps SE might not be the right place to ask this - please comment before down-voting.

Tags : github


Related Questions






Caching assets in website served from Github pages

Updated August 01, 2018 17:03 PM