Periodically rebase firebase-cpp-sdk with upstream

[kendalharland]

Description

This workflow runs thebrowsercompany/gha-sync-fork at 8 am every day.

It can also be triggered manually using:

gh workflow run 'cron-sync-with-upstream.yml' -R thebrowsercompany/firebase-cpp-sdk

Or by clicking the "Sync this Fork" button in the GitHub UI.

Testing

See this workflow run: https://github.com/thebrowsercompany/firebase-cpp-sdk/actions/runs/9104534949

[tristanlabelle]

This is so cool! You should share it with eng-platform-infra :).

What's the flow to handle rebase failures? Once we have one conflicting commit in our history, will all subsequent rebases fail?

[compnerd]

Nice! This seems like the right approach. I still think that there is some value in compressing all the CI changes that we have as their history doesn't actually give us anything.

[kendalharland]

Nice! This seems like the right approach. I still think that there is some value in compressing all the CI changes that we have as their history doesn't actually give us anything.

Agreed! Let's talk about this today: We can either squash the changes periodically, or I can add a parameter to the gha-sync-fork workflow that attempts to do it automatically every time we sync.

What's the flow to handle rebase failures? Once we have one conflicting commit in our history, will all subsequent rebases fail?

Yep, and someone will have to fix the conflict to get this job to succeed again. let's also talk about this today too. We could have some alerting if needed, but I'd like to hear how everyone thinks that alerting should work, and any other ideas we may have.