Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that issues must be created before PRs #2530

Merged
merged 2 commits into from
May 13, 2022
Merged

Clarify that issues must be created before PRs #2530

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bd32f07
Clarify that issues must be created before PRs
tigrannajaryan May 10, 2022
40c500a
Merge branch 'main' into feature/tigran/clarify-issue-pr
reyang May 13, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,19 @@ Agreement](https://identity.linuxfoundation.org/projects/cncf).
Significant changes should go through the [OpenTelemetry Enhancement
Proposal](https://github.com/open-telemetry/oteps) process.

Small changes, such as clarifications, wording changes, spelling/grammar
corrections, etc. can be made directly via pull requests.
Smaller changes can follow a shorter process:

- [Create an issue](https://github.com/open-telemetry/opentelemetry-specification/issues/new/choose)
in this repo and describe the proposed change.
- Follow the [issue workflow](#issue-triaging) and make sure the issue is accepted with
a "Yes" response. If the response to the issue is not "Yes" then do not create a PR
that implements the change since it will be rejected.
- Once the issue is accepted the assignee can work on it and create a PR that implements
the change described in the issue.

Trivial changes, such as clarifications, wording changes, spelling/grammar
corrections, etc. can be made directly via pull requests and do not require an associated
issue.

## Writing specs

Expand Down