Tags contained in issue fork triggers pipelines (and should not)
Problem/Motivation
As reported and discussed in this Slack thread, a rebase to an issue fork that also contains tags coming from the main project, triggers pipelines on those tags in the issue fork. But those pipelines are fairly irrelevant, as the code based on those tags is likely outdated by the time the rebased code is being pushed.
Steps to reproduce
This happened in a contrib project. The rebase push brought the tags 2.0.2, 2.0.3 and 2.0.4 with it and that triggered 3 pipelines on outdated code. Looking at the tag list of the issue fork, we can see that none of the tags triggered pipelines, except those 3 that got created by the rebase push.
Proposed resolution
Prevent tag-based pipeline triggers in issue forks.