-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
auto-merge-autosquash #64
Comments
As I've feared, today I noticed the first attempted murder of my elaborate commit messages: Perhaps an improved solution would be:
|
Agreed that PRs merged in commits like |
At the moment we're using GH's API to merge https://developer.github.com/v3/pulls/#merge-a-pull-request-merge-button, so it's not a simple option to do our own merge strategy. |
I'll remove the auto-merge-squash labels until the commit message issues are properly resolved. |
Looking at the current review queue for the DLang-Bot, this might take a while :/ FWIW isn't it easier to explain to @andralex that you don't want sensible commits to be squashed? |
Currently the bot only has a ref to the PR as merge message, thus all commit messages of the squashed PR are lost, until that get's fixed the feature is outright broken. |
But that's intended! If you don't trust the contributors to use it properly, that's a big statement about the circle of trust... |
It doesn't even preserve the first commit message! We need to at least preserve what github proposes as commit message when you manually squash. |
see #66 |
Only few people will use it, but I'm for teaching dlang-bot to understand |
FYI I just re-enabled the |
GitHub now shows diffs for force-pushes, so this feature suggestion is no longer useful. People should just force-push instead of pushing |
Idea from @CyberShadow:
The text was updated successfully, but these errors were encountered: