chore: automate merging develop to next minor branch

[paulbalandan]

Description
Source: https://github.com/everlytic/branch-merge

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[michalsn]

Won't it produce too many unnecessary commits? Also, there is a question about conflicts.

[paulbalandan]

Hmm, you're right. Maybe instead of every push to develop we can set the action to on: workflow_call? This means we can manually merge thru the GitHub platform directly instead of using local computer.

[michalsn]

Yes, that would be better. But I wonder if the merge commit will be marked as verified.

[paulbalandan]

It seems it's not the case unless we use a PAT and setup signing info in the repo.

[paulbalandan]

I'll close this for now.