From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [COMMITTED][PATCH] ci/wiki-mirror: Fix triggering CI
Date: Mon, 17 Jan 2022 09:19:04 +0000 [thread overview]
Message-ID: <61E534C5.6060005@fujitsu.com> (raw)
In-Reply-To: <20220117090744.30354-1-pvorel@suse.cz>
Hi Petr
> Matching github.repository instead of
> github.event.pull_request.head.repo.full_name is what is required for
> our workflow pushing directly to git (we very rarely use pull requests,
> and not for big changes which includes doc changes).
>
> This also revert 820cfe539b as it didn't fix the problem.
>
> Fixes: 760fdf3a8f ("ci: Don't run wiki mirror on LTP forks")
>
> Signed-off-by: Petr Vorel<pvorel@suse.cz>
> ---
> Hi Xu,
>
> FYI ba99b81708 ("doc: Fix typo missing s in .all_filesystems")
> verified it's working:
>
> https://github.com/linux-test-project/ltp/actions/runs/1707090366
I found this problem when doc/* patch isn't the last patch of a
patchset. But here it is a single patch.
Best Regards
Yang Xu
>
> Kind regards,
> Petr
>
> .github/workflows/wiki-mirror.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.github/workflows/wiki-mirror.yml b/.github/workflows/wiki-mirror.yml
> index 302667255b..36c7d8311e 100644
> --- a/.github/workflows/wiki-mirror.yml
> +++ b/.github/workflows/wiki-mirror.yml
> @@ -11,7 +11,7 @@ on:
> jobs:
> mirror:
> runs-on: ubuntu-latest
> - if: ${{ github.event.pull_request.head.repo.full_name == 'linux-test-project/ltp' }}
> + if: ${{ github.repository == 'linux-test-project/ltp' }}
> steps:
> - name: Checkout LTP
> uses: actions/checkout@v2
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-17 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 9:07 [LTP] [COMMITTED][PATCH] ci/wiki-mirror: Fix triggering CI Petr Vorel
2022-01-17 9:19 ` xuyang2018.jy [this message]
2022-01-17 10:13 ` Petr Vorel
2022-01-18 1:11 ` xuyang2018.jy
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=61E534C5.6060005@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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: link
Be 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