Searched full:secrets (Results 1 – 18 of 18) sorted by relevance
20 secrets:43 USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}71 password: ${{ secrets.LLVM_LIT_TEST_PYPI_API_TOKEN }}78 password: ${{ secrets.LLVM_LIT_PYPI_API_TOKEN }}
64 --token "${{ secrets.RELEASE_WORKFLOW_PR_CREATE }}" \66 --branch-repo-token ${{ secrets.RELEASE_WORKFLOW_PUSH_SECRET }} \
52 --token '${{ secrets.GITHUB_TOKEN }}' \75 repo-token: ${{ secrets.ISSUE_SUBSCRIBER_TOKEN }}
44 github-token: ${{ secrets.GITHUB_TOKEN }}
18 repo-token: ${{ secrets.ISSUE_SUBSCRIBER_TOKEN }}
31 --token '${{ secrets.ISSUE_SUBSCRIBER_TOKEN }}' \
34 --token '${{ secrets.ISSUE_SUBSCRIBER_TOKEN }}' \
38 --token '${{ secrets.GITHUB_TOKEN }}' \
25 MAILGUN_API_KEY: ${{ secrets.LLVM_BUGS_KEY }}
80 GH_TOKEN: ${{ secrets.WWW_RELEASES_TOKEN }}
46 USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}69 # Called workflows don't have access to secrets by default, so we need to explicitly pass secrets that we use.70 secrets:71 RELEASE_TASKS_USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}79 # Called workflows don't have access to secrets by default, so we need to explicitly pass secrets that we use.80 secrets:81 RELEASE_TASKS_USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}106 # Called workflows don't have access to secrets b[all...]
90 --token ${{ secrets.GITHUB_TOKEN }} \
19 secrets:86 USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}
83 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
40 secrets:86 USER_TOKEN: ${{ secrets.RELEASE_TASKS_USER_TOKEN }}
32 # $ docker run --env-file <secrets> -it $(docker build -q libcxx/utils/ci)34 # The environment variables in `<secrets>` should be the ones necessary
171 // here http://www.rcollins.org/secrets/opcodes/SALC.html
112 required to not hold secrets, see below for detailed limitations). This131 *mis*-speculated paths from leaking secrets from memory (and stalls849 fail to leak any secrets. This doesn't end up working because the processor is