open-telemetry
/
opentelemetry-dotnet
mirror of https://github.com/open-telemetry/opentelemetry-dotnet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minor tweak to contrib docs (#2920)

This commit is contained in:
Cijo Thomas 2022-02-22 16:27:17 -08:00 committed by GitHub
parent 71c22ac6a5
commit 69e08c0b62
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CONTRIBUTING.md
View File

@ -114,14 +114,6 @@ Add your fork as an origin:
git remote add fork https://github.com/YOUR_GITHUB_USERNAME/opentelemetry-dotnet.git git remote add fork https://github.com/YOUR_GITHUB_USERNAME/opentelemetry-dotnet.git
``` ```
By default your work will be targeting the `main` branch. If you want to work on
the experimental metrics feature, please switch to the `metrics` feature branch:
```sh
# only do this when you want to work on the experimental metrics feature
git checkout metrics
```
Run tests: Run tests:
```sh ```sh
@ -174,8 +166,8 @@ A PR is considered to be **ready to merge** when:
* Urgent fix can take exception as long as it has been actively communicated. * Urgent fix can take exception as long as it has been actively communicated.
Any Maintainer can merge the PR once it is **ready to merge**. Note, that some Any Maintainer can merge the PR once it is **ready to merge**. Note, that some
PR may not be merged immediately if repo is being in process of a major release PRs may not be merged immediately if the repo is in the process of a release and
and the new feature doesn't fit it. the maintainers decided to defer the PR to the next release train.
If a PR has been stuck (e.g. there are lots of debates and people couldn't agree If a PR has been stuck (e.g. there are lots of debates and people couldn't agree
on each other), the owner should try to get people aligned by: on each other), the owner should try to get people aligned by: