search

asyncapi / .github

Location of all reusable community health files
29 stars 65 forks source link

Release workflow does not work with non-squash commits #228

Open jonaslagoni opened 1 year ago

jonaslagoni commented 1 year ago

Describe the bug

If you have a long-lived branch such as next, and master is updated you will have to do a merge commit (not squash) when updating next with the latest master changes, otherwise you will have to solve the same merge conflicts over and over again. The problem is this approach means that the release workflow will not work.

A workaround is that when you do the merge you have to use fix or feat as commit message (on the local branch) otherwise the release workflow wont be triggered.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart: