Closed CountBleck closed 6 months ago
Do you know why our release pipeline does not work?
I found the reason, aspublish requires breaking / feat / fix
prefix to identifier the version upgrade. Maybe we need to create an action and check the PR title to avoid this weird empty PR. WDYT?
@HerrCai0907 That would be nice, but if a PR only has one commit, the default commit title in the merge commit is based off of that commit's title, not the PR title (see #2826).
@HerrCai0907 That would be nice, but if a PR only has one commit, the default commit title in the merge commit is based off of that commit's title, not the PR title (see #2826).
Yes. But we can switch the merge strategy in configuration page. I am not sure who has the access to setup it. Maybe it needs @dcodeIO or @MaxGraey
@HerrCai0907 that doesn't sound ideal...
Configuration like this:
Why is it not ideal?
Changed the setting to "Pull request title" as suggested
Why is it not ideal?
@HerrCai0907 Oh I misunderstood (I thought you meant switching away from squash merging). That's perfect!
This is a dummy commit to create a new release.