diff --git a/.github/workflows/codeql-analysis.yml b/.github/workflows/codeql-analysis.yml index 3a1fd12d..f6afeeea 100644 --- a/.github/workflows/codeql-analysis.yml +++ b/.github/workflows/codeql-analysis.yml @@ -2,9 +2,9 @@ name: CodeQL on: push: - branches: [master] + branches: [main] pull_request: - branches: [master] + branches: [main] workflow_dispatch: jobs: diff --git a/.github/workflows/nodejs.yml b/.github/workflows/nodejs.yml index 699ed24d..5f3a4208 100644 --- a/.github/workflows/nodejs.yml +++ b/.github/workflows/nodejs.yml @@ -2,9 +2,9 @@ name: Node.js on: pull_request: - branches: [master] + branches: [main] push: - branches: [master] + branches: [main] workflow_dispatch: jobs: diff --git a/.github/workflows/typescript.yml b/.github/workflows/typescript.yml index cfd706fe..1866ca78 100644 --- a/.github/workflows/typescript.yml +++ b/.github/workflows/typescript.yml @@ -2,9 +2,9 @@ name: TypeScript on: pull_request: - branches: [master] + branches: [main] push: - branches: [master] + branches: [main] workflow_dispatch: jobs: diff --git a/.gitmodules b/.gitmodules index 55fde93d..1b5d5983 100644 --- a/.gitmodules +++ b/.gitmodules @@ -11,4 +11,4 @@ [submodule "tests/json-test-suite"] path = tests/json-test-suite url = https://github.com/nst/JSONTestSuite.git - branch = master + branch = main diff --git a/docs/06_custom_tags.md b/docs/06_custom_tags.md index 0ca17d2c..7d3c7c6f 100644 --- a/docs/06_custom_tags.md +++ b/docs/06_custom_tags.md @@ -99,7 +99,7 @@ stringify( In YAML-speak, a custom data type is represented by a _tag_. To define your own tag, you need to account for the ways that your data is both parsed and stringified. Furthermore, both of those processes are split into two stages by the intermediate AST node structure. -If you wish to implement your own custom tags, the [`!!binary`](https://github.com/eemeli/yaml/blob/master/src/tags/yaml-1.1/binary.js) and [`!!set`](https://github.com/eemeli/yaml/blob/master/src/tags/yaml-1.1/set.js) tags provide relatively cohesive examples to study in addition to the simple examples in the sidebar here. +If you wish to implement your own custom tags, the [`!!binary`](https://github.com/eemeli/yaml/blob/main/src/tags/yaml-1.1/binary.js) and [`!!set`](https://github.com/eemeli/yaml/blob/main/src/tags/yaml-1.1/set.js) tags provide relatively cohesive examples to study in addition to the simple examples in the sidebar here. ### Parsing Custom Data diff --git a/docs/07_parsing_yaml.md b/docs/07_parsing_yaml.md index 7abcb39f..d9d7ce5d 100644 --- a/docs/07_parsing_yaml.md +++ b/docs/07_parsing_yaml.md @@ -171,7 +171,7 @@ For debug purposes, if the `LOG_TOKENS` env var is true-ish, all lexical tokens ### CST Nodes -For a complete description of CST node interfaces, please consult the [cst.ts source](https://github.com/eemeli/yaml/blob/master/src/parse/cst.ts). +For a complete description of CST node interfaces, please consult the [cst.ts source](https://github.com/eemeli/yaml/blob/main/src/parse/cst.ts). Some of the most common node properties include: