Rename the "master" branch to "main"
Unless Github redirects workflows that reference the mavenLicenseCheck.yml at the master branch this might break many workflows, e.g.
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/293dc413730b9335d1981bcde47dcc183837f98c/.github/workflows/licensecheck.yml#L21
But I see a chance that redirection will happen automatically and if not we could add/keep the master branch as ordinary other branch for a grace period that's simply not updated anymore and inform users to update their workflows. Or we just break them after announcing it in advance. This way at least it doesn't get unnoticed.
Maintaining the branch for a grace period makes sense to me.
Is there any easy way to get a complete list of adopters?
If not, I may be able to extend the Git indexer script to find them...
Is there any easy way to get a complete list of adopters?
Not that I'm aware of.
If not, I may be able to extend the Git indexer script to find them...
That would be nice to have. But if it's too complicated, a broadcast on the cross-project mailing list seems also sufficient to me.
It would be good to scope the problem. It should only take a few minutes to build a script.
Based on the results, we can determine how wide of a net we need to cast to make sure that nobody gets left behind.