CI within OpenMRS - Bamboo vs Travis vs GitHub Actions vs Azure Pipelines

There’s a somewhat separate but related issue: travis-ci.org shuts down on December 31st [ref]. This affects the vast majority of Travis builds we are currently running. Given the lack of clarity that Travis can provide around their plans for supporting OSS, are there any objections to starting to migrate OpenMRS modules using Travis to GitHub actions?

To be clear, I’m only talking about migrating repositories which are standard OpenMRS modules (so, setting aside OpenMRS infrastructure related projects and the MF stuff) and only those that are clearly not relying on, e.g., Travis secrets and, again, only for PRs and commits to the main branch. I’ll still leave releases, etc. for Bamboo.