[Idea][Feature request] Allow to setup base project for GHActions / CI verification

[Marcin Bonk]

Hello there,

As within company we would like to move our open-source projects (mainly Symfony bundles / Sylius plugins) we would like to get them successfully approven.

However, right now CI builds up package based on symfony/standard which in our case is insufficient, as Sylius is shipped with it's own "standard" version built on top of Symfony, with it's own "internal" bundles, configurations etc.

An ideal outcome of this would be one of below:

• Use "base" project based on composer.json's type (which in Sylius's plugin case is sylius-plugin),
• Allow to specify parameter with "base" project in manifest.json (i.e. "template": "sylius/sylius")

Even if any of mentioned above is hard to deal with, or impossible to do, i'm open to suggestions.

--
I'm not sure if i should create this feature request in here, or in symfony/flex repository.

Thanks in advance

[Marcin Bonk]

@Nyholm (sorry to bother you, but you seem to the most active person here)

Can we get an update on this?

Related PR's:
#1303, #1304, #1305, #1306, #1313

[Nicolas Grekas]

Closing as this stalled, also because there are already open PRs where the issue with CI can be discussed.
We don't require CI to be green before merging when we understand the reason why it's red and we are ok with it.