Release logic grabs commit message from latest tag instead of HEAD #144

New Issue

decentral1se · 2021-04-08T13:27:35Z

decentral1se commented

2021-04-08 13:27:35 +00:00

fd97d41524/abra (L1941)

So when I tried to tag latest 1.13.7 Gitea tag, I got the message from the 1.13.6 tag shown but I think it should instead be the message from HEAD.

https://git.autonomic.zone/coop-cloud/abra/src/commit/fd97d41524532c8c9a446612489eefd4e3e52368/abra#L1941 So when I tried to tag latest 1.13.7 Gitea tag, I got the message from the 1.13.6 tag shown but I think it should instead be the message from HEAD.

decentral1se added this to the Beta release milestone 2021-04-08 13:27:35 +00:00

decentral1se added the

bug

label 2021-04-08 13:27:35 +00:00

3wordchant commented

2021-04-08 15:26:36 +00:00

"Get the message from the latest tag" was added for --force, which is intended for overwriting the latest tag instead of adding a new one.

The non---force behaviour should be to get it from the latest commit message, exactly.

"Get the message from the latest tag" was added for `--force`, which is intended for overwriting the latest tag instead of adding a new one. The non-`--force` behaviour should be to get it from the latest commit message, exactly.

decentral1se referenced this issue from a commit

2021-04-17 21:54:58 +00:00

Choose latest commit message for new tags

decentral1se closed this issue

2021-04-17 21:54:58 +00:00

This repo is archived. You cannot comment on issues.