remove stale branches about pytest-httpserver HOT 4 CLOSED

squash merging is already enabled. There are MRs where we want to keep the commits so I wouldn't force it.
I have also removed many branches, and enabled the Automatic delete options. I have some branches which aren't moving forward but I want to keep the contents in case I will have time to work on such as proxy support.

from pytest-httpserver.

@csernazs
basic rule is that each PR should be as small as possible and be self consistent. That leads to the situations that every PR could be and should be squashed.

You can take example of huge projects. CPython, Django, requests, etc

from pytest-httpserver.

We have small PRs but I like that PRs to have commits with descriptive commit messages such as in #166.
These PRs should not have been squashed, and I think it makes no sense to split this PR to 3 PRs.

Having one commit per PR is also fine and I have no problems if someone wants to squash the commits also (personally I prefer to tailor my commits in my git before pushing it to PR but YMMV).

from pytest-httpserver.

with above mentioned PR I would squash and merge together commit messages.
If commits could be separated as different features, then I would do 3 PRs out of 1.

I just share community standards, but it is up to the project to decide which way to go :)

from pytest-httpserver.