public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Eugene Rozenfeld <erozen@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/microsoft/heads/main)] Switch from secrets.GITHUB_TOKEN to secrets.VICTORPAT when waiting for build and test Date: Thu, 22 Feb 2024 20:26:14 +0000 (GMT) [thread overview] Message-ID: <20240222202614.91F0D385842D@sourceware.org> (raw) https://gcc.gnu.org/g:3fa32e63115aad99e3e149737727b0bf13dceb0a commit 3fa32e63115aad99e3e149737727b0bf13dceb0a Author: Eugene Rozenfeld <erozen@microsoft.com> Date: Thu Feb 22 12:25:06 2024 -0800 Switch from secrets.GITHUB_TOKEN to secrets.VICTORPAT when waiting for build and test Diff: --- .github/workflows/update-main.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/update-main.yaml b/.github/workflows/update-main.yaml index 8fd9d91f85e9..e7b5b6754627 100644 --- a/.github/workflows/update-main.yaml +++ b/.github/workflows/update-main.yaml @@ -356,7 +356,7 @@ jobs: shell: bash env: mergeBranch: ${{ needs.parse-failures.outputs.newBranchName }} - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + GITHUB_TOKEN: ${{ secrets.VICTORPAT }} wait-test: name: Waiting on tests with gcc/master merged into vendor/microsoft/main @@ -394,7 +394,7 @@ jobs: shell: bash env: mergeBranch: ${{ needs.parse-failures.outputs.newBranchName }} - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + GITHUB_TOKEN: ${{ secrets.VICTORPAT }} # The text below is marked with a warning header so that it's colored yellow in the logs and will stand out # I couldn't find any documentation on setting text color in printf statements in a GitHub Yaml file so we're using this for now
reply other threads:[~2024-02-22 20:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240222202614.91F0D385842D@sourceware.org \ --to=erozen@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).