Closed rzvxa closed 12 months ago
@alerque Thanks, I'll give the whole thing a read. I don't have any preference for it so I'll just switch to the imperative tense, It was my bad doing it in the past tense in the first place I should've followed the style of older commits.
As for the conventional commits, I've never set up any CI for creating changelogs using conventional commits and/or semver before, But if you don't mind we can add an action for the master branch that releases a new version. Let me know whether or not you are into this idea.
I'd be fine with some release automation, probably with some manual triggering. It could just post a new commit with an updated changelog and tag it appropriately. I would suggest git-cliff
for the job if we try to automate it.
I'll start working on it whenever I find some free time, It may take a weekend or two for me to read all of the documentation and play around with small examples so I have to postpone it until I'm finished with my current project. I need to test it in my own repository but I'll make sure to create a draft merge request when I've got a working version so you can give feedback on the implementation.
I think we should release a new version at this point before merging more PRs. We already have 10 updates on this minor version.