-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove stale branches #169
Comments
squash merging is already enabled. There are MRs where we want to keep the commits so I wouldn't force it. |
@csernazs You can take example of huge projects. CPython, Django, requests, etc |
We have small PRs but I like that PRs to have commits with descriptive commit messages such as in #166. 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). |
with above mentioned PR I would squash and merge together commit messages. I just share community standards, but it is up to the project to decide which way to go :) |
please remove unused branches. Ideally keep only
master
https://github.com/csernazs/pytest-httpserver/branches
For the future auto deleting could be enabled: https://github.com/csernazs/pytest-httpserver/settings
The text was updated successfully, but these errors were encountered: