-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Make new single-commit PR validation optional #159
Comments
Ok, yes – sounds like a fair use case. @kenji-miyake Would you mind adding an opt-in flag like |
No, I don't mind that, but I feel we can discuss it a bit more here. Although I don't deny @mowies's use case, let me confirm:
Anyway, I'll prepare a PR while waiting for the reply! |
@amannn Regarding the CI, should I create |
I think enabling the flag in the existing workflow should be fine. Thanks a lot! |
I'm considering what is the best description for this option... 🤔 |
@amannn How about this one?
|
Signed-off-by: Kenji Miyake <[email protected]>
🎉 This issue has been resolved in version 4.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
FYI: A new option, "Default to PR titles for squash merge commit messages". |
Oh my god, that's fantastic. Thank you so much for sharing this @kenji-miyake! I'll add this to the docs. |
The changes done by @kenji-miyake in #158 are a great addition, but I think they should be configurable through a flag/setting.
I have a few bot-created pull requests where the single commit message has more info that should stay there, but it's not important for the PR reviewer, so in this case I would like to keep the title simple but the commit message should still have more advanced info inside.
Here is an example: keptn/keptn#6789
The text was updated successfully, but these errors were encountered: