Where does the `trigger/*` tag comes from?

[NobodyXu]

After publishing cargo-quickinstall v0.2.9, created tag cargo-quickinstall-v0.2.9 for the test and fixing the e2etest #203 , somehow new tags:

trigger/aarch64-apple-darwin      
trigger/aarch64-unknown-linux-gnu 
trigger/x86_64-apple-darwin       

are created which caused the cronjob to fail.

I greped the *.sh and .github/workflow/* and didn't find any usage of git-tag except in create_tag_and_release.sh which is used in build-version.yml and I didn't see any problem with that.

[NobodyXu]

@alsuren Do you have any idea why is that happening?

[alsuren]

My current guess is that you have them locally and they get pushed whenever you run git push --tags. Delete them locally and then delete them on origin and they should stay gone.

I don't know if it's possible to audit when a tag was made or by who. I think not - I think tools tend to just give you the date/author of the commit.

On Tue, 14 Mar 2023, 07:58 Jiahao XU, @.***> wrote:

@alsuren https://github.com/alsuren Do you have any idea why is that happening?

— Reply to this email directly, view it on GitHub https://github.com/cargo-bins/cargo-quickinstall/issues/204#issuecomment-1467478753, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB6FNZZEBW3YTFF642H74LW4AJKZANCNFSM6AAAAAAV2A6TAE . You are receiving this because you were mentioned.Message ID: @.***>

[NobodyXu]

My current guess is that you have them locally and they get pushed whenever you run git push --tags.

I only remember doing git push though and I didn't remember doing any git tag. Anyway, I removed them from the repository and locally, so let's see if this will happen again.