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)] Add a workflow to test current upstream gcc. Date: Fri, 16 Apr 2021 20:36:26 +0000 (GMT) [thread overview] Message-ID: <20210416203626.4ECB63893662@sourceware.org> (raw) https://gcc.gnu.org/g:a6ff5881b0236647f736b0ba5487c8c1b89e1b7f commit a6ff5881b0236647f736b0ba5487c8c1b89e1b7f Author: Eugene Rozenfeld <erozen@microsoft.com> Date: Fri Nov 13 14:53:21 2020 -0800 Add a workflow to test current upstream gcc. Diff: --- .github/workflows/fetch-rebase-test.yaml | 41 ++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/.github/workflows/fetch-rebase-test.yaml b/.github/workflows/fetch-rebase-test.yaml new file mode 100644 index 00000000000..85133ec749f --- /dev/null +++ b/.github/workflows/fetch-rebase-test.yaml @@ -0,0 +1,41 @@ +name: fetch-rebase-test + +# Run this workflow every week +on: + schedule: + - cron: "0 8 * * 0" + workflow_dispatch: + +jobs: + fetch-rebase-test: + runs-on: ubuntu-18.04 + steps: + - name: Checkout + uses: actions/checkout@v2 + with: + fetch-depth: 0 + submodules: recursive + lfs: true + ref: current + - name: Add remote + run: | + git remote add gcc git://gcc.gnu.org/git/gcc.git + - name: Fetch + run: | + git fetch gcc master + - name: Rebase + run: | + git log gcc/master -1 + git config --global user.email "erozen@microsoft.com" + git config --global user.name "Eugene Rozenfeld" + git rebase gcc/master + - name: Check commits + run: | + git status + git log -15 + + - name: Run build script + run: | + chmod +x .github/scripts/build-gcc.sh + .github/scripts/build-gcc.sh + shell: bash
reply other threads:[~2021-04-16 20:36 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=20210416203626.4ECB63893662@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).