You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like this repo has been master-to-main-ed in the past, but the branch is still called master: #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: guardian/master-to-main#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?
The text was updated successfully, but these errors were encountered:
I have a very vague memory of having to rename this to master as it broke something elsewhere, but cannot remember the details unfortunately. I guess we can try renaming to main and see what happens? We can always rename it back if needed. I think that it's because it's a thrift model and the path in Maven has master in it (not entirely sure) @ParisaTork
Thank you so much for the info @rowannekabalan :) I'll see on Monday if someone familiar with the behaviour of this repo in Ed Tools can test it to see if it works as expected after it gets renamed to main
It looks like this repo has been master-to-main-ed in the past, but the branch is still called master: #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: guardian/master-to-main#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?
The text was updated successfully, but these errors were encountered: