guardian / guardian/content-entity

Repo has been m2m-ed in the past, but branch still called master?

Open
#28 2 comments 0 reactions 2 assignees Claimed by @rowannekabalan View on GitHub
Dominant language
Scala
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

It looks like this repo has been master-to-main-ed in the past, but the branch is still called master: https://github.com/guardian/content-entity/issues/15

Was going to m2m this myself, as I'm m2m-ing the Ed Tools repos and integrating them with Snyk, but this one is a bit of an anomaly: https://github.com/guardian/master-to-main/issues/214

Would it be sufficient to rename the master branch to main, using the GitHub GUI or have there been more references to master/main, since it was m2m-ed a year ago?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.