[GH-ISSUE #5149] gitlab-ci: Automatically run CI checks for all applicable GitHub PRs #2895

New issue

gitea-mirror · 2026-05-05T09:33:38-06:00

gitea-mirror commented

2026-05-05 09:33:38 -06:00

Originally created by @kmk3 on GitHub (May 17, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5149

Pipelines were executed for pull requests that have no relevance to GitLab CI,
such as the following ones about updating the versions of GitHub Actions:

->

But they were not executed for the following pull requests that actually change
the code and/or .gitlab-ci.yml:

@Fred-Barclay @reinerh

Originally created by @kmk3 on GitHub (May 17, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5149 Pipelines were executed for pull requests that have no relevance to GitLab CI, such as the following ones about updating the versions of GitHub Actions: * #5119 * #5128 * #5144 -> * <https://gitlab.com/Firejail/firejail_ci/-/pipelines/523611105> * <https://gitlab.com/Firejail/firejail_ci/-/pipelines/529088107> * <https://gitlab.com/Firejail/firejail_ci/-/pipelines/539786701> But they were not executed for the following pull requests that actually change the code and/or .gitlab-ci.yml: * #5134 * #5147 * #5148 @Fred-Barclay @reinerh

gitea-mirror added the

enhancement

label 2026-05-05 09:33:38 -06:00

gitea-mirror commented

2026-05-05 09:33:40 -06:00

@kmk3 commented on GitHub (May 17, 2022):

Also, can someone add me (same username) to the GitLab project so that I can
debug the CI there?

@kmk3 commented on GitHub (May 17, 2022): Also, can someone add me (same username) to the GitLab project so that I can debug the CI there?

gitea-mirror commented

2026-05-05 09:33:41 -06:00

@reinerh commented on GitHub (May 17, 2022):

Also, can someone add me (same username) to the GitLab project so that I can debug the CI there?

invite sent.

@reinerh commented on GitHub (May 17, 2022): > Also, can someone add me (same username) to the GitLab project so that I can debug the CI there? invite sent.

gitea-mirror commented

2026-05-05 09:33:42 -06:00

@kmk3 commented on GitHub (May 17, 2022):

@reinerh commented on May 17:

Also, can someone add me (same username) to the GitLab project so that I
can debug the CI there?

invite sent.

Thanks!

@kmk3 commented on GitHub (May 17, 2022): @reinerh commented [on May 17](https://github.com/netblue30/firejail/issues/5149#issuecomment-1129089195): > > Also, can someone add me (same username) to the GitLab project so that I > > can debug the CI there? > > invite sent. Thanks!

gitea-mirror commented

2026-05-05 09:33:42 -06:00

@kmk3 commented on GitHub (May 17, 2022):

Regarding the PRs, it looks like the default rule on GitLab CI is something
like "always build on (first-party) branch creation/modification", which by
default would include master and any other branches that exist in this
repository (and any branch that is pushed only to the mirror).

Since dependabot creates the branches directly in this repository (rather than
in a fork), all of its branches also get tested. But branches from forks are
not copied over to the GitLab mirror when a PR is opened, so they are not
tested.

So it should be simple to ignore dependabot PRs based on paths changed or on
branch name, but automatically building PRs opened from forks seems trickier.

I see now that this feature is actually being tracked by GitLab:

Main issue:

Backend: Allow CI/CD mirroring to handle forks on GitHub SCM
(2018-04-13)

Related issues:

Fetch refs/pull/*/head refs for mirror repository (2019-09-05)
Spike: Allow CI/CD mirroring to handle forks on GitHub SCM issue
(2020-11-12)

To anyone reading this, please consider voting on the main issue if you think
it would be useful (it's at +77/-0 votes as of writing).

@kmk3 commented on GitHub (May 17, 2022): Regarding the PRs, it looks like the default rule on GitLab CI is something like "always build on (first-party) branch creation/modification", which by default would include master and any other branches that exist in this repository (and any branch that is pushed only to the mirror). Since dependabot creates the branches directly in this repository (rather than in a fork), all of its branches also get tested. But branches from forks are not copied over to the GitLab mirror when a PR is opened, so they are not tested. So it should be simple to ignore dependabot PRs based on paths changed or on branch name, but automatically building PRs opened from forks seems trickier. I see now that this feature is actually being tracked by GitLab: Main issue: * [Backend: Allow CI/CD mirroring to handle forks on GitHub SCM][1] (2018-04-13) Related issues: * [Fetch `refs/pull/*/head` refs for mirror repository][2] (2019-09-05) * [Spike: Allow CI/CD mirroring to handle forks on GitHub SCM issue][3] (2020-11-12) To anyone reading this, please consider voting on the main issue if you think it would be useful (it's at +77/-0 votes as of writing). [1]: https://gitlab.com/gitlab-org/gitlab/-/issues/5667 [2]: https://gitlab.com/gitlab-org/gitaly/-/issues/1913 [3]: https://gitlab.com/gitlab-org/gitlab/-/issues/281689

Sign in to join this conversation.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2895

Rows
Columns