Unverified Commit 4fc19792 authored by Huseyin ELMAS's avatar Huseyin ELMAS Committed by GitHub

fix(docs): master branch renaming (#33312)

contributing.md file still refers `master` branch name since the branch renamed as `main` recently. This PR contains a fix for that.

**related:**
#33153
#33198

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`
Co-authored-by: 's avatarTim Neutkens <6324199+timneutkens@users.noreply.github.com>
parent 00a84328
...@@ -6,10 +6,9 @@ examples](#adding-examples)** below. ...@@ -6,10 +6,9 @@ examples](#adding-examples)** below.
## Developing ## Developing
The development branch is `canary`, and this is the branch that all pull The development branch is `canary`. This is the branch that all pull
requests should be made against. After publishing a stable release, the changes requests should be made against. The changes on the `canary`
in the `canary` branch are rebased into `master`. The changes on the `canary` branch are published to the `@canary` tag on npm regularly.
branch are published to the `@canary` dist-tag daily.
To develop locally: To develop locally:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment