We have a bunch of projects built with Flowershow template, but we lose track of what version of Flowershow template they use and if we want to upgrade them, we have to overwrite the whole repo with degit and go through all the changes - which is not a trivial task, especially if the project has lots of customizations. Also: we don't really know if we should upgrade any of these projects, until we see that sth doesn't work that should work in the current version of the Flowershow template. And only then we see that we should upgrade.
Can we maybe somehow automatically create PRs in those "dependent" projects with the changes merged to Flowershow's main branch? (Or only when a PR is merged, if we make main protected.) This way we wouldn't have to overwrite the whole repo with degit and go through all the changes, to pick only what's needed - this is cumbersome and messy. We would only have to deal with latest changes, latest PR merged to main.
We have a bunch of projects built with Flowershow template, but we lose track of what version of Flowershow template they use and if we want to upgrade them, we have to overwrite the whole repo with degit and go through all the changes - which is not a trivial task, especially if the project has lots of customizations. Also: we don't really know if we should upgrade any of these projects, until we see that sth doesn't work that should work in the current version of the Flowershow template. And only then we see that we should upgrade.
Can we maybe somehow automatically create PRs in those "dependent" projects with the changes merged to Flowershow's main branch? (Or only when a PR is merged, if we make
mainprotected.) This way we wouldn't have to overwrite the whole repo with degit and go through all the changes, to pick only what's needed - this is cumbersome and messy. We would only have to deal with latest changes, latest PR merged to main.Is this even feasible?