Closed adeeena closed 2 years ago
Sorry for not seeing this sooner. New job uses github, which means notifications from this repo kinda vanish in the flood of work related PRs.
@adeeena secrets.GITHUB_TOKEN
is only scoped for the repo running the workflow. You don't have commit rights to this repo, so it's failing.
Rather than commit them, how about having it produce an artifact? I'm planning to construct my existing workflow into a proper deployment script that generates an artifact, so I could tack this on as an extra job and combine the two artifacts for push to S3.
There we go. I'll iterate on it further, but this is an excellent start. Thanks!
Remarks:
The exported pdfs go to another branch (
export-pdfs
), for manual verification (before it goes directly on public), also to check whether a github action, which performs push on itself will re-trigger another action, possibly causing an infinite build loop.I added links to the PDFs to each language, however apart from Hungarian I had to rely on Google Translate for the labels. Please verify (DE @TheBlackAlpha48 , PL @ErdaradunGaztea , CN-ZH @rqnj )
Reading the action yaml, you might find that I'm working on a translation for another language.
Why the checks failing? the .yml file tries to do the push on the {current user}/GenderDysphoria.fyi, which is
adeeena
in this PR.