Deployment cronjob creates tag but it doesn't trigger `deploy-tag` about browser-extension-template HOT 5 CLOSED

Added personal token to secrets with name GH_TOKEN (not GITHUB_TOKEN, which is reserved by GHA).

Lets use this repo for testing, I thinks we can change cron as we need.

from browser-extension-template.

That’s a slightly confusing name (too similar to the included token), in RG I proposed to store it as TAGGER_TOKEN to justify why it’s needed at all.

Anyway that PR was merged so we can wait until April 4th to see if it works there.

from browser-extension-template.

RG finally create a new tag but it still didn't trigger the deploy-tag workflow

According to that forum, the problem was also that @actions was the tag committer, so maybe changing that would work. Sending a PR now

from browser-extension-template.

Still didn't work. I may have found a better solution Nope.

Edit: I don't understand why it's not working... the docs say it should

from browser-extension-template.

The holy grail is here: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjobs_idoutputs

• Have a job detect the need for a release
• Have following jobs depend on that, and use it as a condition 🎉

from browser-extension-template.