feat: detect all package changes

[SMillerDev]

This should allow us to use this flow in homebrew/cask too.

[MikeMcQuaid]

Looks good so far!

I guess it feels a little half-way for now; I'd probably rather it either moves to entirely moving things over to packages or having separate formulae/casks for variables and flags. There's probably always going to warrant a need for some different classes for Formulae*/Casks*

[SMillerDev]

Doesn't every tap use this function by default? That would be a lot of people who suddenly have their tap broken if we remove the formulae_ variables.

I'm fine splitting up the variables and/or making a combination. But just to make sure: you're only talking about this method right? You're not looking for me to add casks to all flags in this PR.

[MikeMcQuaid]

Doesn't every tap use this function by default? That would be a lot of people who suddenly have their tap broken if we remove the formulae_ variables.

It does but we can/should change that in Homebrew/brew and add a deprecation.

I'm fine splitting up the variables and/or making a combination. But just to make sure: you're only talking about this method right? You're not looking for me to add casks to all flags in this PR.

I think it's fine to have for now but I guess I'm a little confused as to how it ends up being useful when only detection is done and nothing else?

[SMillerDev]

Since detection is a separate step, it allows me to move another part of cask CI to testbot.

Everything after that will take more work so I'd like to do them separately

[MikeMcQuaid]

Since detection is a separate step, it allows me to move another part of cask CI to testbot.

Ok, makes sense. If it's useful as-is: great.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[SMillerDev]

Updated to be specific to casks.

[MikeMcQuaid]

Great work, thanks @SMillerDev!

[MikeMcQuaid]

Good to 🚢 when CI is 🟢

[SMillerDev]

I have no clue why CI could be failing, as far as I can tell it should be bright green

[MikeMcQuaid]

Invalid usage: Did not find any formulae or commits to test!

Looks like CI is perhaps legitimately broken.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.