chore: change .github branches

Author: yaoleyaotouoO

.github/CONTRIBUTING.md

@@ -2,9 +2,10 @@
 
 Hi! I’m really excited that you are interested in contributing to Formily. Before submitting your contribution though, please make sure to take a moment and read through the following guidelines.
 
-- [Issue Reporting Guidelines](#issue-reporting-guidelines)
-- [Pull Request Guidelines](#pull-request-guidelines)
-- [Git Commit Specific](./GIT_COMMIT_SPECIFIC.md)
+- [Contributing Guide](#contributing-guide)
+  - [Issue Reporting Guidelines](#issue-reporting-guidelines)
+  - [Pull Request Guidelines](#pull-request-guidelines)
+  - [Git Commit Specific](#git-commit-specific)
 
 ## Issue Reporting Guidelines
 
@@ -26,8 +27,8 @@ Hi! I’m really excited that you are interested in contributing to Formily. Bef
 
 ## Pull Request Guidelines
 
-- Only code that's ready for release should be committed to the master branch. All development should be done in dedicated branches.
-- Checkout a **new** topic branch from master branch, and merge back against master branch.
+- Only code that's ready for release should be committed to the main branch. All development should be done in dedicated branches.
+- Checkout a **new** topic branch from main branch, and merge back against main branch.
 - Work in the `src` folder and **DO NOT** checkin `dist` in the commits.
 - Make sure `npm test` passes.
 - If adding new feature:

.github/ISSUE_TEMPLATE/config.yml

@@ -4,7 +4,7 @@ contact_links:
     url: https://formilyjs.org/guide/issue-helper
     about: The issue which is not created via https://formilyjs.org/guide/issue-helper will be closed immediately.
   - name: ✨ Question Answer / Idea
-    url: https://github.com/alibaba/formily/discussions/new
+    url: https://github.com/formilyjs/vant/discussions/new
     about: All questions can be solved here. At the same time you can provide all your ideas here.
   - name: 📖 View documentation
     url: https://formilyjs.org

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +1,7 @@
 _Before_ submitting a pull request, please make sure the following is done...
 
-- [ ] Ensure the pull request title and commit message follow the [Commit Specific](https://github.com/alibaba/formily/blob/formily_next/.github/GIT_COMMIT_SPECIFIC.md) in **English**.
-- [ ] Fork the repo and create your branch from `master` or `formily_next`.
+- [ ] Ensure the pull request title and commit message follow the [Commit Specific](https://github.com/formilyjs/vant/blob/main/.github/CONTRIBUTING.md#git-commit-specific) in **English**.
+- [ ] Fork the repo and create your branch from `main`.
 - [ ] If you've added code that should be tested, add tests!
 - [ ] If you've changed APIs, update the documentation.
 - [ ] Ensure the test suite passes (`npm test`).

.github/workflows/ci.yml

@@ -3,10 +3,10 @@ name: Node CI
 on:
   push:
     branches:
-      - master
+      - main
   pull_request:
     branches:
-      - master
+      - main
 
 jobs:
   build:

.github/workflows/commitlint.yml

@@ -6,9 +6,9 @@ name: Check Commit spec
 on:
   # Triggers the workflow on push or pull request events but only for the formily_next branch
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:

.github/workflows/release.yml

@@ -3,7 +3,7 @@ name: Release
 on:
   push:
     branches:
-      - formily_next
+      - main
 jobs:
   release:
     runs-on: ubuntu-latest
@@ -12,6 +12,7 @@ jobs:
       - uses: actions/checkout@v1
         with:
           fetch-depth: 0
+          ref: main
       - uses: actions/setup-node@v1
         with:
           node-version: 12