gitlab sync action workflow fails for PR from forked repo

[sverhoeven]

Describe the bug
I have a (Pull Request)[https://github.com//pull/810] made from a forked repo which mails me about a failed workflow run, but then on PR page the failure is not visible.

To Reproduce
Steps to reproduce the behavior, if relevant, provide the input that triggered the error:

1. I created a PR Round other cluster + dont add score which was not there before #810
2. I get a mail with failed worklow run https://github.com/i-VRESSE/haddock3/actions/runs/7972092429
3. In PR conversation I see a red check in the last commit, but once the other workflows have completed everything is green.

Expected behavior
For branches in forked repo that the https://github.com/i-VRESSE/haddock3/blob/main/.github/workflows/github-to-gitlab-push-sync.yml workflow does not run.

[rvhonorato]

This is related to the action implemented by @amjjbonvin in #798 which was wrongly done.

It can be safely ignored in forked repos, but the action itself needs to be re-configured

[amjjbonvin]

I would not know how to re-configure it.
It is working for the mirroring to the EU Castiel GitLab (was checked by the reviewers actually)

[sverhoeven]

Adding a condition similar to integration test would exclude syncing of branches in forked repos.
See

haddock3/.github/workflows/tests.yml

Line 61 in 2550d55

if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository }}

[rvhonorato]

I would not know how to re-configure it. It is working for the mirroring to the EU Castiel GitLab (was checked by the reviewers actually)

It can be both wrong and working 😉

[rvhonorato]

Should be fixed now @sverhoeven 🤞🏽

[sverhoeven]

Should be fixed now @sverhoeven 🤞🏽

Great, that is good for any external contributors.