Default branch for projects within terraform-google-modules

[wyardley]

Component

Git

TL;DR

The default branch for this project, as well as most projects I've seen within https://github.com/terraform-google-modules/, is master, however, many / most Google projects have already long since switched to main.

Are there any major obstacles (hard-coded branch names, branch protection rules, release configs, etc.) that make switching over too difficult to be worth it?

Setting aside the ideological, it would be convenient when switching between projects.

Detailed design

No response

Additional information

No response

[bharathkkb]

This should be straightforward since GH redirects but we should still test it on one repo first.

[wyardley]

@bharathkkb there might be some CI configs (like the lint target) or build triggers (on the cloudbuild side) that need to be updated as well, but I didn't find too much in the repos themselves other than that one - seems like the release-please configuration is pretty simple.

Some of the workflows / triggers could include a pattern for both branches so it could be done ahead of the switch.