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 calling test-composite action Date: Tue, 27 Feb 2024 19:37:25 +0000 (GMT) [thread overview] Message-ID: <20240227193725.74F933858C41@sourceware.org> (raw) https://gcc.gnu.org/g:8e4796dcdde9cd0508306868ab79a6bf054ed5f3 commit 8e4796dcdde9cd0508306868ab79a6bf054ed5f3 Author: Eugene Rozenfeld <erozen@microsoft.com> Date: Mon Feb 26 12:00:17 2024 -0800 Switch from secrets.GITHUB_TOKEN to secrets.VICTORPAT when calling test-composite action Diff: --- .github/workflows/test-gcc.yaml | 2 +- .github/workflows/update-main.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/test-gcc.yaml b/.github/workflows/test-gcc.yaml index 8f3516ead47..625a4b497f3 100644 --- a/.github/workflows/test-gcc.yaml +++ b/.github/workflows/test-gcc.yaml @@ -138,7 +138,7 @@ jobs: with: configjson: ${{needs.init.outputs.config}} testSet: ${{ matrix.testSet }} - githubtoken: ${{ secrets.GITHUB_TOKEN }} + githubtoken: ${{ secrets.VICTORPAT }} buildDownloaded: False - name: Move objdir to be in repo so logs inside can be uploaded diff --git a/.github/workflows/update-main.yaml b/.github/workflows/update-main.yaml index e7b5b675462..caa589715f8 100644 --- a/.github/workflows/update-main.yaml +++ b/.github/workflows/update-main.yaml @@ -189,7 +189,7 @@ jobs: with: configjson: ${{needs.gcc-master-build.outputs.config}} testSet: ${{ matrix.testSet }} - githubtoken: ${{ secrets.GITHUB_TOKEN }} + githubtoken: ${{ secrets.VICTORPAT }} buildDownloaded: True - name: Move objdir to be in repo so logs inside can be uploaded
next reply other threads:[~2024-02-27 19:37 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-27 19:37 Eugene Rozenfeld [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-02-26 20:06 Eugene Rozenfeld
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=20240227193725.74F933858C41@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).