Deployment error on new repo without pull requests

[jbusecke]

I just noticed a quirk with the deploy action for a brand new repo where the action was entirely triggered by pushes to main.

I was trying to separate a recipe example from a more mature and complex bakery repo and ran into this error.

assert len(pulls) == 1  # pretty sure this is always true, but just making sure

I think this line here basically fails because there is not a single PR in the repo yet (will test this in a minute). But just wanted to document this here.

[cisaacstern]

Yes the error should presumably be more descriptive.

But in general I think this is the behavior we want?

Insofar as it ensures users are not deploying by pushing to main (but rather from PRs)?

[jbusecke]

I think this is worth a broader discussion (pending some docs write up) as I have been going back and forth on how to actually launch recipes in multiple scenarios (see #33).