Migration to using main branch (onnx#3925)

* add warning announce

Signed-off-by: Chun-Wei Chen <[email protected]>

* Rename to main branch globally

Signed-off-by: Chun-Wei Chen <[email protected]>

Author: jcwchen

.azure-pipelines/Linux-CI.yml

@@ -1,5 +1,5 @@
 trigger:
-- master
+- main
 
 jobs:
 - job: 'Test'

.azure-pipelines/MacOS-CI.yml

@@ -1,5 +1,5 @@
 trigger:
-- master
+- main
 
 jobs:
 - job: 'Test'

.azure-pipelines/Windows-CI.yml

@@ -1,5 +1,5 @@
 trigger:
-- master
+- main
 
 jobs:
 

.github/workflows/release_linux_aarch64.yml

@@ -5,9 +5,9 @@ on:
     # Run weekly on Monday 00:00
     - cron:  '00 00 * * MON'
   push:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   pull_request:
-    branches: [rel-*, master]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 jobs:

.github/workflows/release_linux_i686.yml

@@ -5,9 +5,9 @@ on:
     # Run weekly on Monday 00:00
     - cron:  '00 00 * * MON'
   push:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   pull_request:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 jobs:

.github/workflows/release_linux_x86_64.yml

@@ -5,9 +5,9 @@ on:
     # Run weekly on Monday 00:00
     - cron:  '00 00 * * MON'
   push:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   pull_request:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 jobs:

.github/workflows/release_mac.yml

@@ -5,9 +5,9 @@ on:
     # Run weekly on Monday 00:00
     - cron:  '00 00 * * MON'
   push:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   pull_request:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 # Use MACOSX_DEPLOYMENT_TARGET=10.12 to produce compatible wheel

.github/workflows/release_win.yml

@@ -5,9 +5,9 @@ on:
     # Run weekly on Monday 00:00
     - cron:  '00 00 * * MON'
   push:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   pull_request:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 jobs:

.github/workflows/weekly_mac_ci.yml

@@ -8,7 +8,7 @@ on:
     # run weekly on Sunday 23:59
     - cron:  '59 23 * * SUN'
   pull_request:
-    branches: [master, rel-*]
+    branches: [main, rel-*]
   workflow_dispatch:
 
 jobs:

.github/workflows/win_no_exception_ci.yml

@@ -2,9 +2,9 @@ name: Windows_No_Exception_CI
 
 on:
    push:
-    branches: [ master, rel-* ]
+    branches: [ main, rel-* ]
    pull_request:
-    branches: [ master, rel-* ]
+    branches: [ main, rel-* ]
 jobs:
   build:
     runs-on: windows-latest

CONTRIBUTING.md

@@ -24,7 +24,7 @@ Attend ONNX Steering Committee meetings - they are open to all in the community.
 
 ## Contributing code
 
-You can submit a pull request (PR) with your code. The [SIG](https://github.com/onnx/onnx/blob/master/community/sigs.md) or [Working Group](https://github.com/onnx/onnx/blob/master/community/working-groups.md) that is responsible for the area of the project your PR touches will review it and merge once any comments are addressed.
+You can submit a pull request (PR) with your code. The [SIG](community/sigs.md) or [Working Group](community/working-groups.md) that is responsible for the area of the project your PR touches will review it and merge once any comments are addressed.
 
 ### DCO
 ONNX has adopted the [DCO](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin). All code repositories under ONNX require a DCO. (ONNX previously used a CLA, which is being replaced with the DCO.)
@@ -38,7 +38,7 @@ NOTE: the sign-off is needed for each commit in the PR, not at the PR level.
 If you have old commits that are not signed, use the following commands to squash the old PR (original branch) into a single commit. This is an easier way to signoff old commits in old PR.
 
 ```bash
-git checkout master
+git checkout main
 git checkout -b temporary_patch              # create a new branch as temporary
 git merge --squash original_patch            # copy from old branch
 git branch -d original_patch                 # remove old branch

README.md

@@ -1,10 +1,10 @@
 <!--- SPDX-License-Identifier: Apache-2.0 -->
 
-<p align="center"><img width="40%" src="https://github.com/onnx/onnx/raw/master/docs/ONNX_logo_main.png" /></p>
+<p align="center"><img width="40%" src="https://github.com/onnx/onnx/raw/main/docs/ONNX_logo_main.png" /></p>
 
-[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/7?label=Linux&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=7&branchName=master)
-[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/5?label=Windows&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=5&branchName=master)
-[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/6?label=MacOS&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=6&branchName=master)
+[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/7?label=Linux&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=7&branchName=main)
+[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/5?label=Windows&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=5&branchName=main)
+[![Build Status](https://img.shields.io/azure-devops/build/onnx-pipelines/onnx/6?label=MacOS&logo=Azure-Pipelines)](https://dev.azure.com/onnx-pipelines/onnx/_build/latest?definitionId=6&branchName=main)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/3313/badge)](https://bestpractices.coreinfrastructure.org/projects/3313)
 
 [Open Neural Network Exchange (ONNX)](https://onnx.ai) is an open ecosystem that empowers AI developers
@@ -29,6 +29,9 @@ ONNX is [widely supported](http://onnx.ai/supported-tools) and can be found in m
 * [Graph Optimization](https://github.com/onnx/optimizer)
 * [Opset Version Conversion][version_converter]
 
+# NOTICE: ONNX now uses main branch as default branch
+Here are the [steps](https://github.com/onnx/onnx/wiki/How-to-migrate-to-main-branch-in-local-repo) from ONNX wiki for migrating to main branch in local repo.
+
 # Contribute
 ONNX is a [community project][community]. We encourage you to join the effort and contribute feedback, ideas, and code. You can participate in the [SIGs][sigs] and [Working Groups][wgs] to shape the future of ONNX.
 
@@ -273,7 +276,7 @@ pytest
 
 # Development
 
-Check out the [contributor guide](https://github.com/onnx/onnx/blob/master/docs/CONTRIBUTING.md) for instructions.
+Check out the [contributor guide](https://github.com/onnx/onnx/blob/main/docs/CONTRIBUTING.md) for instructions.
 
 # License
 
@@ -289,17 +292,17 @@ NOTE: these are absolute rather than repo-relative because we
 this document is rendered by PyPI which doesn't seem to handle
 relative links properly. See https://github.com/dhimmel/obonet/issues/12.
 -->
-[overview]: https://github.com/onnx/onnx/blob/master/docs/Overview.md
-[ir]: https://github.com/onnx/onnx/blob/master/docs/IR.md
-[versioning]: https://github.com/onnx/onnx/blob/master/docs/Versioning.md
-[operators]: https://github.com/onnx/onnx/blob/master/docs/Operators.md
-[python_api]: https://github.com/onnx/onnx/blob/master/docs/PythonAPIOverview.md
-[shape_inference]: https://github.com/onnx/onnx/blob/master/docs/ShapeInference.md
-[version_converter]: https://github.com/onnx/onnx/blob/master/docs/VersionConverter.md
-[new_op]: https://github.com/onnx/onnx/blob/master/docs/AddNewOp.md
-[community]: https://github.com/onnx/onnx/tree/master/community
-[sigs]: https://github.com/onnx/onnx/tree/master/community/sigs.md
-[wgs]: https://github.com/onnx/onnx/tree/master/community/working-groups.md
-[contributing]: https://github.com/onnx/onnx/blob/master/docs/CONTRIBUTING.md
-[CMakeLists]: https://github.com/onnx/onnx/blob/master/CMakeLists.txt
-[license]: https://github.com/onnx/onnx/blob/master/LICENSE
+[overview]: https://github.com/onnx/onnx/blob/main/docs/Overview.md
+[ir]: https://github.com/onnx/onnx/blob/main/docs/IR.md
+[versioning]: https://github.com/onnx/onnx/blob/main/docs/Versioning.md
+[operators]: https://github.com/onnx/onnx/blob/main/docs/Operators.md
+[python_api]: https://github.com/onnx/onnx/blob/main/docs/PythonAPIOverview.md
+[shape_inference]: https://github.com/onnx/onnx/blob/main/docs/ShapeInference.md
+[version_converter]: https://github.com/onnx/onnx/blob/main/docs/VersionConverter.md
+[new_op]: https://github.com/onnx/onnx/blob/main/docs/AddNewOp.md
+[community]: https://github.com/onnx/onnx/blob/main/community
+[sigs]: https://github.com/onnx/onnx/blob/main/community/sigs.md
+[wgs]: https://github.com/onnx/onnx/blob/main/community/working-groups.md
+[contributing]: https://github.com/onnx/onnx/blob/main/docs/CONTRIBUTING.md
+[CMakeLists]: https://github.com/onnx/onnx/blob/main/CMakeLists.txt
+[license]: https://github.com/onnx/onnx/blob/main/LICENSE

RELEASE-MANAGEMENT.md

@@ -11,7 +11,7 @@ Releases are versioned according to [ONNX Versioning](docs/Versioning.md). This
 
 On a regular basis, new versions of ONNX are published, representing the aggregate of changes in the IR and operator sets. Such releases use semantic versioning to describe the progression of the standard.
 
-The GitHub repo for ONNX provides release branches where the project is stabilized as per the process described here. Release notes are used to communicate the stability and status of a release. The master branch will be used to continue work for subsequent releases.
+The GitHub repo for ONNX provides release branches where the project is stabilized as per the process described here. Release notes are used to communicate the stability and status of a release. The main branch will be used to continue work for subsequent releases.
 
 Major, minor and patch releases will have branch names and version numbers reflecting the nature of the change as per semantic versioning definitions.
 
@@ -33,7 +33,7 @@ to be produced.
 
 - The release manager announces the initial commit for testing. The first
   period lasts a week; any regressions found should be fixed, typically via
-  the master branch. Incomplete features should be done or excised during this
+  the main branch. Incomplete features should be done or excised during this
   period. A distribution can be made available with an -RC1 suffix.
 
 - The release manager announces a second round of testing (unless it's only a

community/sc-election-guidelines.md

@@ -4,9 +4,9 @@
 
 ## Introduction
 
-To encourage community participation and wider adoption in the industry, ONNX has introduced [open governance](https://github.com/onnx/onnx/wiki/Expanded-ONNX-Steering-Committee-Announced!) in March 2018. The governance has three defined structures to propel the development of ONNX project forward: [Steering Committee](https://github.com/onnx/onnx/tree/master/community#steering-committee), [Special Interest Groups (SIGs)](https://github.com/onnx/onnx/tree/master/community#sig---special-interest-groups), and [Working Groups (WGs)](https://github.com/onnx/onnx/tree/master/community#wg---working-groups). While SIGs and WGs primarily focus on the techinical roadmap of ONNX, the Steering Committe is responsible for setting the vision and governance process of the ONNX community.
+To encourage community participation and wider adoption in the industry, ONNX has introduced [open governance](https://github.com/onnx/onnx/wiki/Expanded-ONNX-Steering-Committee-Announced!) in March 2018. The governance has three defined structures to propel the development of ONNX project forward: [Steering Committee](/community/readme.md#steering-committee), [Special Interest Groups (SIGs)](/community/readme.md#sig---special-interest-groups), and [Working Groups (WGs)](/community/readme.md#wg---working-groups). While SIGs and WGs primarily focus on the techinical roadmap of ONNX, the Steering Committe is responsible for setting the vision and governance process of the ONNX community.
 
-For the first year of its ONNX open governance, representatives from Facebook, Microsoft, AWS, Intel and Nvidia are chosen to serve as the ONNX Steering Committee to help guide the project. The Steering Committee will be elected by the [Contributors](https://github.com/onnx/onnx/tree/master/community#community-roles) in its second year and will be re-elected every year.
+For the first year of its ONNX open governance, representatives from Facebook, Microsoft, AWS, Intel and Nvidia are chosen to serve as the ONNX Steering Committee to help guide the project. The Steering Committee will be elected by the [Contributors](/community/readme.md#community-roles) in its second year and will be re-elected every year.
 
 This document is created to provide guidelines for the election process to ensure maximum transparency and fairness.
 
@@ -28,7 +28,7 @@ Candidate applications will be accepted in April, and the election will be held
 ## Eligibility
 
 ### Eligibility for Steering Committee candidacy
-Candidates will be self-nominated, and they do not necessarly need to be a [Contributor](https://github.com/onnx/onnx/tree/master/community#community-roles) to the ONNX project. The duties of the Steering Committee extend beyond simply contributing code to the ONNX project.
+Candidates will be self-nominated, and they do not necessarly need to be a [Contributor](/community/readme.md#community-roles) to the ONNX project. The duties of the Steering Committee extend beyond simply contributing code to the ONNX project.
 
 
 ### Eligibility for voting

community/sigs.md

@@ -2,7 +2,7 @@
 
 # SIGs - Special Interest Groups
 
-As described in the ONNX [governance](https://github.com/onnx/onnx/tree/master/community#sig---special-interest-groups), Special Interest Groups (SIGs) are persistent groups responsible for specific parts of the project. SIGs have open and transparent proceedings to develop goals and implement code contributions. SIGs are also responsible for ongoing maintenance of the code in their areas.
+As described in the ONNX [governance](/community/readme.md#sig---special-interest-groups), Special Interest Groups (SIGs) are persistent groups responsible for specific parts of the project. SIGs have open and transparent proceedings to develop goals and implement code contributions. SIGs are also responsible for ongoing maintenance of the code in their areas.
 
 ## Joining a SIG
 

community/working-groups.md

@@ -2,7 +2,7 @@
 
 # Working Groups
 
-As described in the ONNX [governance](https://github.com/onnx/onnx/tree/master/community#wg---working-groups), Working Groups (WGs) are temporary groups formed to address issues that cross SIG boundaries. Working Groups have a have a clear goal measured through specific deliverables and disband after the goal is achieved. Working groups do not own artifacts long term; they create specifications, recommendations, and/or code implementations for submission to the relevant SIGs for approval and acceptance.
+As described in the ONNX [governance](/community/readme.md#wg---working-groups), Working Groups (WGs) are temporary groups formed to address issues that cross SIG boundaries. Working Groups have a have a clear goal measured through specific deliverables and disband after the goal is achieved. Working groups do not own artifacts long term; they create specifications, recommendations, and/or code implementations for submission to the relevant SIGs for approval and acceptance.
 
 ## Proposing a new working group
 New Working Groups are created when there is sufficient interest in a topic area and someone volunteers to be the chair for the group and submits a proposal to the steering committee. The chair facilitates the discussion and helps synthesize proposals and decisions.