Emoncms V9.9.6 Stable merge (pre-merge check)

aha looks like I got the ordering wrong then, merging to stable prior to setting the tab. If I merge master again into stable now would that then include the tag perhaps?

What is the reason for the annotated tag?

Github will also create the tag for you if you just create a release in the UI…?

I think doing the tag is the very last thing and it attaches itself to the last commit. I’d just point the tag to the right commit.

git describe will easily identify where the user’s repository is for the admin page.

Github tags are ‘lightweight’ tags, using the -a creates annotated tags. Have a look at the reference for a fuller explanation.

so the git describe of 9.9.4-207-g0a74cda9 is on commit g0a74cda9 which is 207 commits ahead of the last annotated tag 9.9.4

$ git describe --tags --debug
searching to describe HEAD
 lightweight        1 9.9.6
 lightweight      190 9.9.5
 lightweight      204 9.9.3
 annotated        207 9.9.4
 lightweight      258 V9.9.2

Thanks @borpin Il take a look and get back to you on this soon.

1 Like