When an update release repo is forked from the mainline stabilization repo, we setup a mirror job to propagate tags from the stabilization repo to the update repo (e.g. tags in jdk22 are mirrored to jdk22u). We are able to do that thanks to the "tags: only" configuration option. However, for "jfx22", there is no separate repo, it's just a branch in "jfx", so if we were to setup such a job there, we would include tags both for the jfx22 and the jfx23 release, which is not what we want.

We need some way of filtering which tags are included when mirroring only tags. I see two ways we could solve this:

1. We could introduce a tags pattern configuration, similar to the branch patterns. However I think this would require the bot to run "git push" for every tag matching the pattern every time, which would not scale well.

2. We could use the git --follow-tags option, but that would require us to also push the branch that the desired tags belong to. I don't think pushing that branch would actually be that bad, but others may disagree. In the jfx example that would mean mirroring the "jfx22" branch from the "jfx" repo to the "jfx22u" repo and include all tags on commits in that branch.

I'm not sure what way we should go here.