Rare project developers

[Alexander Gall <>]

On Wed, 8 Feb 2023 12:12:20 +0100, mc36 <> said:

> hi,
> On 2/8/23 12:09, Alexander Gall wrote:
>> 
>>> Sure, then we'll know if this things finally works :)
>> 
>> Ok, so now the problem is this (you would see this in the Bitbucket
>> webhook page if you had access):
>> 
>> Ignoring push type BRANCH, action UPDATE for ID master on commit 
>> 724d4000daf75dbb7d09b76caef1ac413d8fa840
>> (Trigger set to TAG/ADD/optimize_profiles)
>> 
>> How exactly did you move the tag to get this as an "update" instead of
>> "add"? When I do it, I generate a "delete" followed by a "add". But
>> maybe I could just treat "update" like "add" :/
>> 

> mc36@rare:~/rare$ history | tail -5
>    628  ./update.sh
>    629  ./update-src.sh
>    630  git tag -af optimize_profiles
>    631  git push origin --tags --force
>    632  history | tail -5
> mc36@rare:~/rare$

Ok, I guess --force results in the UPDATE. I now accept that as well,
should be fine. Please try again, but I think now you have to
explicitely delete the tag first (to trigger the webhook on the same
commit)

$ git push origin :optimize_profiles
$ git push origin optimize_profiles

Also, the tag doesn't have to be annotated, but that should also be
irrelevant, except that you'll see a different commit ID reported by
the optimizer (annotated tags have their own commit which act as an
alias for the commits you see in the commit log).

-- 
Alex