-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠️ Update the default branch of the Apollo Server repository. #4302
Conversation
This makes it more permanent anyways.
According to the documentation for `package.json` (referenced below), this is the correct way to reference packages that live within a monorepo within the `package.json`. Ref: https://docs.npmjs.com/files/package.json#repository
Historically, there have been a few varieties chosen here, but we should keep them all the same now that we have a standard that has emerged!
This PR will result in a release being created for this repository.
Well, that did not work as expected. When this PR merged, many PRs were re-targeted, but most were closed. I've contacted GitHub Support and am going to open a pinned issue. EDIT: Fixed! See #4304 for details. |
did I miss any april's fools? |
I'm curious, what was this change for? |
don't say it out loud, but probably has to do with this rare movement that thinks the word "master" refers to slavery. |
@gentunian you hit the mark. Git and GitHub are reportedly also moving towards releasing an update where this will become standard after said update. It's a |
Thanks, for sure changing branches naming will make this world a better place. Glad to see this coming. |
This PR will result in a release being created for this repository. Apollo-Orig-Commit-AS: apollographql/apollo-server@aa22b2c
…l/master Apollo-Orig-Commit-AS: apollographql/apollo-server@a2d2792
This PR changes the default branch of this repository to
main
from its previous name,master
. While this could be done exclusively in the UI (and that change has been made already), this is being opened as a PR for a few reasons:With the recent introduction of automatic pull-request retargeting by GitHub, this will happen automatically when this PR is merged.
I've pushed the housekeeping commits to make this change whole to the (no longer default!)
master
branch which this PR is opened from. There are a couple additional changes which I've put into this PR, mainly around alignment of patterns within this repository and adopting thedirectory
notation withinpackage.json
'srepository
specifications. See the individual commits for details.