...]'
##[error]Git command 'git -C /tmp/tagbot_repo_11_28_w8 rev-parse ' failed
Exiting with status 1
```
I double checked that the tagbot workflow file in the repo is as specified at the top of this Discourse post. A similar process worked on one of my other repo’s a few days ago, so this might be a common problem higher up rather than local repos?
Thanks in advance for any help!
EDIT:
```julia
Run JuliaRegistries/TagBot@v1
INPUT_TOKEN -e INPUT_REGISTRY -e INPUT_BRANCHES -e INPUT_DISPATCH -e INPUT_DISPATCH_DELAY -e INPUT_LOOKBACK -e INPUT_SSH -e INPUT_SSH_PASSWORD -e INPUT_GPG -e INPUT_GPG_PASSWORD -e INPUT_CHANGELOG -e INPUT_CHANGELOG_IGNORE -e HOME -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e GITHUB_ACTIONS=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/DistributedFactorGraphs.jl/DistributedFactorGraphs.jl":"/github/workspace" degraafc/tagbot:1
Processing version v0.6.0 (d8aa89814f4ee4451491ad9a053782c4945b6670)
Generating changelog for version v0.6.0 (d8aa89814f4ee4451491ad9a053782c4945b6670)
Creating release v0.6.0 at d8aa89814f4ee4451491ad9a053782c4945b6670
Exiting with status 0
```
---
### Author:  [@laborg](https://discourse.julialang.org/u/laborg)
#### Post date: [February 21, 2020, 6:06pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/46 "2020-02-21T18:06:33Z")
The default TagBot.yaml (as written in the first post) is scheduled to run every hour. Can anyone share insights about the resource cost of such a run? So is this just a single http call or is there a more involved machinery in play like e.g. docker container startup etc…?
It should be made more visible what this Tagbot does to allow better informed decision on how to use it. In my use case of a library that changes rarely, the Tagbot is either a resource hog when configured to be run often, or results in a large tagging “latency” in the other case.
Maybe this can be achieved with a simple comment in the TagBot.yaml template above the cron line. e.g: `# spin up ubuntu virtual machine and check repository for tag-action every hour`. (…or whatever the TagBot actually does).
---
### Author:  [@christopher-dG](https://discourse.julialang.org/u/christopher-dG)
#### Post date: [February 21, 2020, 6:30pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/47 "2020-02-21T18:30:43Z")
> [@eford](#):
>
> I merged the PR as requested. However, then I got an error email
> [@dehann](#):
>
> HI, I’m getting something similar with Tagbot not creating a new release as expected
My bad guys! I pushed a new version but forgot one step of the release process. I’m working on setting up automatic error reporting without actually failing the action so you aren’t notified of this stuff in the future, as well as a more reliable, automated release process.
> [@laborg](#):
>
> Can anyone share insights about the resource cost of such a run?
TagBot runs in a Docker container, so yes, there is some overhead. Usually it’ll run for ~30 seconds including all that overhead. I think it’s pretty reasonable for people to reduce the frequency to once a day.
---
### Author:  [@dpo](https://discourse.julialang.org/u/dpo)
#### Post date: [April 23, 2020, 4:19pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/48 "2020-04-23T16:19:59Z")
I’m getting spammed by messages of the form
```julia
Run failed for master (3ddf6fa)
Repository: JuliaSmoothOptimizers/PROPACK.jl
Workflow: TagBot
Duration: 0.0 seconds
Finished: 2020-04-23 16:05:52 UTC
View results
Jobs:
```
Is there anything to do about them? The message says nothing about what failed or why. How do I make them stop?
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [April 23, 2020, 4:46pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/49 "2020-04-23T16:46:27Z")
I don’t know if it’s related, but today GitHub had issues (again): [GitHub Status - Incident on 2020-04-23 13:20 UTC](https://www.githubstatus.com/incidents/2y6v4ltq26g7). Also, I’d suggest to reduce the frequency of TagBot to once per day (maybe at a time different from midnight UTC)
---
### Author:  [@tbeason](https://discourse.julialang.org/u/tbeason)
#### Post date: [April 23, 2020, 5:37pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/50 "2020-04-23T17:37:38Z")
I have also been getting several emails about TagBot runs failing.
---
### Author:  [@dlfivefifty](https://discourse.julialang.org/u/dlfivefifty)
#### Post date: [April 24, 2020, 9:58am UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/51 "2020-04-24T09:58:05Z")
I think you opt out of email notifications
---
### Author:  [@christopher-dG](https://discourse.julialang.org/u/christopher-dG)
#### Post date: [April 24, 2020, 2:27pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/52 "2020-04-24T14:27:28Z")
Yeah GH has been truly awful for this as of late… I also recommend to reduce the frequency to once daily.
What I really want is to not have to use the cron trigger and have something that reacts to the registry… AKA the old GitHub App 😅 Despite the benefits of using Actions, sometimes I regret switching over when stuff like this happens.
---
### Author:  [@c42f](https://discourse.julialang.org/u/c42f)
#### Post date: [May 22, 2020, 3:05am UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/53 "2020-05-22T03:05:41Z")
What if JuliaRegistrator commented back in the package repo after the new version PR was merged in the General registry? Could you then trigger the workflow based on that comment?
---
### Author:  [@christopher-dG](https://discourse.julialang.org/u/christopher-dG)
#### Post date: [May 22, 2020, 10:13pm UTC](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344/54 "2020-05-22T22:13:52Z")
> [@c42f](#):
>
> What if JuliaRegistrator commented back in the package repo after the new version PR was merged in the General registry?
This has been discussed [here](https://github.com/JuliaRegistries/TagBot/issues/125). I definitely support that strategy but some other concerns were raised.
Unrelated, but I’ve been considering creating a new TagBot as an OAuth application that supports a whole bunch of languages/package registries… Maybe one day I’ll get acquired by GitHub like Dependabot did 😅
[Previous page](https://discourse.julialang.org/t/ann-the-tagbot-github-app-is-deprecated-in-favour-of-the-tagbot-github-action/34344.md?page=2)