-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Migrate from "master" branch to "main" #11715
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/23937/ |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 8bf0b7f:
|
Repl is fixed by babel/website#2277, and it's unrelated to this PR. |
@@ -137,7 +137,7 @@ To enable the Node.js debugger added in v6.3.0, set the `TEST_DEBUG` environment | |||
$ TEST_DEBUG=true make test | |||
``` | |||
|
|||
You can combine `TEST_DEBUG` with `TEST_GREP` or `TEST_ONLY` to debug a subset of tests. If you plan to stay long in the debugger (which you'll likely do!), you may increase the test timeout by editing [test/mocha.opts](https://github.com/babel/babel/blob/master/test/mocha.opts). | |||
You can combine `TEST_DEBUG` with `TEST_GREP` or `TEST_ONLY` to debug a subset of tests. If you plan to stay long in the debugger (which you'll likely do!), you may increase the test timeout by editing [test/testSetupFile.js](https://github.com/babel/babel/blob/main/test/testSetupFile.js). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link was wrong
@@ -13,7 +13,7 @@ | |||
"bugs": { | |||
"url": "https://github.com/babel/babel/issues" | |||
}, | |||
"homepage": "https://github.com/babel/babel/tree/master/eslint/babel-eslint-parser", | |||
"homepage": "https://babeljs.io/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what we are doing with almost all the other packages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also replace babel/babel/blob/master
by babel/babel/blob/main
in ./docs/**/*.md
of babel-website
.
* Remove dead link * Use consistent "homepage" url in package.json * Update md links * Update comment link in parser d.ts * Add comment in gitpod config * Update circleci config * Update PULL_REQUEST_TEMPLATE * Update badges * Trigger CI * Update 404 link
As per discussion on Slack, this PR is migrating from
master
tomain
.master
because it would cause problems to all the existing PRs.master
tomain
master
so that we don't accidentally merge PRs into it.The REPL should already work but it doesn't. I'll investigate why.Unrelated - babel/website#2277While I was doing this, I also enabled
test262
on thenext-8-*
branches.