4 Commits

Author	SHA1	Message	Date
P0nk	4004b36bfa	Tag the merge commit instead of last commit in the PR ... The merge commit is more suitable since it provides some context and groups up all the commits.	2022-10-16 11:53:29 +02:00
P0nk	584fccec92	Activate bump-version action	2022-10-16 10:04:35 +02:00
P0nk	e12d853499	Update build workflow - new name and updated dependencies	2022-10-16 08:48:32 +02:00
P0nk	5c7fcdae06	Add action to automatically tag commits ... Using this action: https://github.com/marketplace/actions/github-tag-bump The idea is that the repo will be versioned in SemVer format, such as "v0.5.3". When a PR is merged, a new version will automatically be added. The new version is generated based on the latest tag, and the part that is bumped is dictated by the merge commit message, either #major, #minor (default) or #patch. This way I (the repo owner) has control over versioning, and other contributors don't have to bother with anything.	2022-10-16 08:34:45 +02:00