Modify main GitHub action to include other configurations and auto-generated changelog

[soumyamahunt]

1. This PR makes the Notepads CI/CD Pipeline action to run for other configurations like old build action used to do. The conditions are adjusted so Sonarcloud only runs with Production configuration, while for both Debug and Release config only build is tested.
2. Added auto generated changelog.
3. Introduced ignoring execution with documentation or other unnecessary changes.

PR Type

What kind of change does this PR introduce?

Feature

[aleks-ivanov]

@Jasonstein @soumyamahunt these are all very beneficial improvements to the current versioning process, but before merging please wait for the PR with the automatic versioning for comparison, because the steps concerning the versioning are removed and replaced by a completely different implementation

[soumyamahunt]

@Jasonstein @soumyamahunt these are all very beneficial improvements to the current versioning process, but before merging please wait for the PR with the automatic versioning for comparison, because the steps concerning the versioning are removed and replaced by a completely different implementation

I have made this PR draft and will retarget it to the new automatic versioning PR once that becomes live.

[0x7c13]

Is this your own version of tag action?

[soumyamahunt]

I was about to comment about this, I opened a PR in the action repo that will allow notepads to use the tag action without having to follow semver style tags. Currently I am keeping this for testing, but if the PR accepted we will follow the main repo.

[0x7c13]

@Jasonstein I have some suggestion about release strategy. Right now any push commit with the proper format triggers a release, the drawback of this is the changelog will only contain that specific commit and you will have to later modify changelog. What I want to propose is trigger release with workflow_dispatch event with an input, this way we can always follow the format for all commits and the changelog will be generated from appropriate commits without requiring you to modify anything later.

100% agreed.

[soumyamahunt]

@Jasonstein I have some suggestion about release strategy. Right now any push commit with the proper format triggers a release, the drawback of this is the changelog will only contain that specific commit and you will have to later modify changelog. What I want to propose is trigger release with workflow_dispatch event with an input, this way we can always follow the format for all commits and the changelog will be generated from appropriate commits without requiring you to modify anything later.

[soumyamahunt]

@Jasonstein I have changed the release process, have a look on the documentations and let me know if I should change anything.