This might be too specific to how we structure our releases and charts, but essentially they're all contained in a single repository, and new charts and releases typically get added at the same time via a PR. One issue we've run into is, if the chart a release references isn't currently in the base branch (i.e. master), the CI checks will fail. This PR checks if the charts repo specified in a release is the same as the repo currently being tested, and if it is, tries to checkout the same branch.
If this solution isn't general purpose enough, we could have this be non-default behaviour enabled via an environment variable.
This might be too specific to how we structure our releases and charts, but essentially they're all contained in a single repository, and new charts and releases typically get added at the same time via a PR. One issue we've run into is, if the chart a release references isn't currently in the base branch (i.e.
master), the CI checks will fail. This PR checks if the charts repo specified in a release is the same as the repo currently being tested, and if it is, tries to checkout the same branch.If this solution isn't general purpose enough, we could have this be non-default behaviour enabled via an environment variable.