# Tagbot is not tagging releases automatically

**URL:** <https://discourse.julialang.org/t/tagbot-is-not-tagging-releases-automatically/61712>\
**Category:** General Usage\
**Tags:** package, registry, general-registry, tagbot\
**Created:** [May 24, 2021, 8:58am UTC](https://discourse.julialang.org/t/tagbot-is-not-tagging-releases-automatically/61712 "2021-05-24T08:58:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)\
**Post date:** [May 24, 2021, 8:58am UTC](https://discourse.julialang.org/t/tagbot-is-not-tagging-releases-automatically/61712/1 "2021-05-24T08:58:42Z")

</div>

In my package [SphericalHarmonics.jl](https://github.com/jishnub/SphericalHarmonics.jl) the tagbot has not been tagging releases. My [TagBot.yml](https://github.com/jishnub/SphericalHarmonics.jl/blob/master/.github/workflows/TagBot.yml) is

```julia
name: TagBot
on:
  issue_comment:
    types:
      - created
  workflow_dispatch:
jobs:
  TagBot:
    if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
    runs-on: ubuntu-latest
    steps:
      - uses: JuliaRegistries/TagBot@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          ssh: ${{ secrets.DOCUMENTER_KEY }}

```

which I guess is the recommended workflow. Currently I have to manually trigger the TagBot after a release is merged. Is there a way to fix this?

If it matters, I have registered a fork of an earlier package that was unregistered.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [May 24, 2021, 9:49am UTC](https://discourse.julialang.org/t/tagbot-is-not-tagging-releases-automatically/61712/2 "2021-05-24T09:49:27Z")

</div>

TagBot works by commenting in an issue. You have issues disabled in your fork