feat: compare changes in current with master branch to get selectors

[Skisocks]

Previously only the most recent commit was used to identify changes to a helmfile and identify the selectors to use. This caused issues where if a second commit was made altering a different helmfile then the first helmfile would be ignored. This is fixed by comparing changes to the helmfiles in the current branch with what is currently in the default branch.

The --allow-no-matching-release flag has also been added. This stops the templating from erroring in the case where a namespace is removed (selector applied to the helmfile flags no longer exists).

[jenkins-x-bot]

Hi @Skisocks. Thanks for your PR.

I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[Skisocks]

/cc @msvticket

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign msvticket
You can assign the PR to them by writing /assign @msvticket in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[msvticket]

While this already is an improvement there is another case I'd like you to handle:
A change has been made to another helmfile on the "master" branch. That is you should consider all files that differ between the PR branch and master.

We are really only interested in those changes that have not been regenerated, but it is quite tricky to find out.

So you could use this git log command:

git log $defaultBranch...HEAD --name-only --pretty=format:

And then there is another case I don't see is considered: that the script isn't run on a PR branch, but on master.