CI: job not started because spending limit needs to be increased

[pjonsson]

I have enabled CI jobs to run in my forked terriajs-repository that I submit PRs from, and I just got this message:

The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.

I'm a free user and the repository is public so I'm guessing Github (wrongly) decided I hit the storage quota or similar, because there is an upload of yarn.lock for each deploy job.

The upload of yarn.lock was added in #6382 for debug reasons. Would it be possible to flip things around, so the yarn.lock is required to be updated in the commit instead, and the debug upload could be removed?

I got tired of frequently having an out-of-date yarn.lock a couple of days ago and prepared #7467 to deal with that problem.

Every PR I make from my forked terriajs repository also fails the deploy job since I don't have your secrets. When should the deploy job run, is it sufficient to only run it on merges to the main branch?