Description
/area registry
Currently, when commits are made to the devfile/registry repository, AppSRE's pipelines automatically build and deploy the devfile registry to staging. However, when changes are delivered to the other registry repositories (such as devfile/registry-support or devfile/registry-viewer), these changes do not get reflected into the staging registry (and production) until a new commit is made in the registry repository. There should be a mechanism that automatically triggers a build and deploy of the staging registry when commits are made to registry-support (and eventually registry-viewer).
GitHub provides support for repository dispatches to trigger actions in other repositories, which we use in the registry-support repository. We should set up a GitHub action that triggers a build and deploy for the staging registry, via an empty commit in devfile/registry (with commit text something like Trigger devfile registry deploy ...). This action should run whenever changes are merged into the main branch in registry-support (and eventually registry-viewer).
The flow would look like the following:
