Github: individual requests for unrelated minor changes?

Question

I just saw Github from a contributor perspective, so here is the question for the maintainers:

When I make several changes that are all unrelated (for example, improve documentation, fix the Rakefile, test and fix a minor bug), is it easier for maintainers if I associate them with a single pull request (using, say, a misc-fixes with with three unrelated entries), or do I need to create separate branches with one pull request?

I suppose that as soon as I have serious or potentially controversial changes, it is better to have a separate request for stretching, so it can be discussed, and supporters do not need to choose cherry if they want to pull my other changes. But if the changes are minor, what are the arguments for and against combining multiple commits into the misc-fixes branch?

Answer 1

The industry on the job is usually the backup server for a long development effort, i.e. It requires several commits, each of which represents an intermediate stable state of the code base.

But for some fast evolutions that don't change the stability of the code (it still compiles and passes the tests), a single commit (and then a single pull request) is enough.