2 years ago

https://www.linkedin.com/in/kevin-luu-3485a01a/ Here at https://hubs.li/Q011Rfby0, we power release automation with ephemeral environments. We recently worked with a customer that leverages git submodules and requested our assistance in triggering an ephemeral environment on https://hubs.li/Q011Rfby0 on every submodule update. If you do not know what submodules are and are curious, you can find more information https://git-scm.com/book/en/v2/Git-Tools-Submodules. Customer Scenario https://www.linkedin.com/in/vickykoblinski The customer has a GitHub repository, which we will refer to as the parent repository, that uses a couple of dependent submodules.

The customer wanted a custom GitHub Action to trigger whenever any of the submodules are updated to create a new branch on the parent repository, create a pull request against the master branch, thus spinning up a new ephemeral environment to test and validate the new changes.