Closed MKyhos closed 2 years ago
Great :) The release functionality needs probably some more work, I will it just merge it as is and fix it on the go then?
RE workfow: Yes I would say:
dev
. Also probably, edit some NEWS.md
main
. Then, on main:dev
is again ahead of main
, increase version number by some patch number etcOr did I miss something? :)
@MKyhos thanks for the explanation. I put it down here: https://github.com/CorrelAid/kbtbr/wiki/Releasing-kbtbr i always get a bit confused with the releases and the tags. is it correct to use the lightweight tags to tag before releasing? or does it even matter that much?
A tag is needed beforehand, so it is used while creating the Release to refer to a certain version of the code
Im GitHub UI kann man glaube ich aber auch im Release dialog direkt dort den Tag anlegen, wenn es noch keinen passenden gibt
This PR adds a makefile to support basic dev workflows.
Note: the release functionality is not yet ready, will work a bit more on this later.