1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-30 08:09:15 +01:00
Commit Graph

5 Commits

Author SHA1 Message Date
ricky
eb241ae68f
bump crowdin/github-action (#14475) 2022-04-20 15:46:53 -04:00
ricky
2b134a0c7f
Update crowdin/github-action (#14381)
* Use crowdin/github-action@1.4.7

* use SHA
2022-04-07 14:28:03 -04:00
ricky
405a3495b0
Update crowdin workflow config (#13494)
* Add metamaskbot GH_USERNAME and GH_EMAIL to env

* add additional config for token, github_user_name, github_user_email

* delete

* delete token

* add GITHUB_ACTOR

Co-authored-by: Alex Donesky <adonesky@gmail.com>
2022-02-04 13:51:11 -05:00
ricky
f58e2552c3
use PAT for GITHUB_TOKEN (#13307)
Use `secrets.METAMASKBOT_CROWDIN_TOKEN` for `GITHUB_TOKEN`

ref: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

> When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
2022-01-13 17:45:07 -05:00
ricky
163d472fdf
Add crowdin configuration and github action (#12552)
* add crowdin.yml

* add crowdin_action.yml

* remove comments

* test on this branch

* use SHA

* only run on develop
2021-12-09 16:53:58 -05:00