Add auto-updating CHANGELOG.md on develop branch

[riyenas0925]

Is your feature request related to a problem? Please describe.

• Add auto-updating CHANGELOG.md on develop branch

Describe the solution you'd like

• Currently, only apply automatically to the main branch
• Using the matrix function of Github actions, both develop and main branches will be applied automatically.

[riyenas0925]

@soimkim
There are no conflicts, but I checked that the commits were duplicated.
I'll think of a new way to PR again. Thanks for the feedback 😄

[riyenas0925]

@soimkim
I've tried a number of ways, but I'm having problems for the following reasons

case 1

advantages : There is no duplicated of commit
disadvantages : Main Branch is a previous release of changelog

To prevent duplicate commits, if you create a changelog in the develop branch and merge it into the main branch, both branches have the same changelog. However, since the changelog is created after the release has been published, this method ensures that the develop branch has the latest changelog, but the main branch has the changelog of the previous release.

case 2

advantages : All branches are the latest release of changelog.
disadvantages : Duplicate occurrence of commitment

If you commit the change log in both develop and master branches, it will work as follows, but the same commit will be duplicated when merged into main later.

case 3

This is a method of adding the changelog to the develop branch before merging in PR and then proceeding with the merge. But it failed because it was before release.

conclusion

I think it would be difficult to change the changelog without committing in the develop branch because all the methods are released in the main branch. Therefore, In the second case, if duplicate commits are displayed separately into Update Changelog on develop branch and Update Changelog on main branch, wouldn't duplication be avoided?

I'd like to hear from the maintainer Thank you!

[soimkim]

Are you saying that each commit in case 2 is left with a different commit message so it's not a duplicate commit?
That seems like the best way. 👍

[riyenas0925]

@soimkim
Thank you for your comments!