fregante/browser-extension-template

Deployment cronjob creates tag but it doesn't trigger `deploy-tag`

fregante opened this issue · 5 comments

fregante commented

There is a limitation of workflow: An action in a workflow run can't trigger a new workflow run.

I would suggest you use your own PAT when creating tags. You can store your PAT in secrets and use ${{ secrets.PATNAME } in your actions.

env:
  GITHUB_TOKEN: ${{ secrets.PATNAME }}

From: https://github.community/t5/GitHub-Actions/Github-actions-workflow-not-triggering-with-tag-push/m-p/39772#M3959

You can see this in Refined GitHub’s Actions. "Auto-tagger" ran but "Deployment" didn't follow it. Now I had to re-create the tag

rgh

I think this only needs to be updated with instructions to use a custom personal token instead of the provided one.

notlmn commented

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.

fregante commented

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.

fregante commented

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

fregante commented

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

fregante commented

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 🎉