9 Commits

Author SHA1 Message Date
P0nk
f61fee829a Upgrade Java version and dependencies 2024-05-09 11:45:16 +02:00
Ponk
9def444442 Fix version bump not obeying merge commit message (#157) #patch
* Fix version bump not obeying merge commit message

* Test the fix to bump-version

* Fix reference to specific tag of github-tag-action

* Dummy patch commit #patch

* Clean up testing of bump-version
2022-12-27 15:07:12 +01:00
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
P0nk
ef70dac1a0 Bump to Java 17 2022-02-12 17:22:54 +01:00
P0nk
958fa657cd Configure Actions for Java 16 2021-09-06 21:23:57 +02:00
Ponk
306f403f18 Set up Actions PR pipeline (#18)
Create Actions PR pipeline - this will automatically run on opened Pull Requests to make sure they compile and pass all (future) tests.
2021-04-10 11:21:40 +02:00