[feature/calens-changelog-actions] Automated Calens Changelog Creation

[hosy]

Description

This PR uses GitHub Actions to automatically generate a changelog file with Calens and commits the new CHANGELOG.md into the current branch.
Furthermore the PR template was updated with new checkboxes to get sure, that a release notes issue file for Calense was added.

Related Issue

Motivation and Context

Automatically changelog file creation, with the same structure, as other ownCloud repositories.

How Has This Been Tested?

• Add an release notes issue file into changelog/unreleased with the issue number as file name
• Commit and push to git
• Check GitHub Actions
• As a result the CHANGELOG.md file should be updated

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[TheOneRing]

does it need to be that old? I think 16.04 is eol.

[hosy]

What do you prefer? 20.04?

[TheOneRing]

changelog/CHANGELOG.md
I guess you copied it from desktop, that file was committed by accident 🙈

[hosy]

changelog/CHANGELOG.md
I guess you copied it from desktop, that file was committed by accident 🙈

I used the file and folder structure from the client repo.

[TheOneRing]

LGTM

[micbar]

Looking god so far.

If you would like to take a look in ocis, we managed to do release and Full changelog with only a single template.

[micbar]

Do you use Calens in the release process?

We do that in ocis like this https://github.com/owncloud/ocis/blob/master/.drone.star#L914

It pushes the single version changes into gitHub releases.

https://github.com/owncloud/ocis/blob/master/.drone.star#L934

[hosy]

@micbar thank you for your hint. Calens will be processed after each commit in the related branch.
I can have a look creating a GitHub release automatically, when a new tag was detected.