Skip to content

Commit

Permalink
first commit
Browse files Browse the repository at this point in the history
  • Loading branch information
ZenoCC-Peng committed Jun 23, 2023
0 parents commit a7921d3
Show file tree
Hide file tree
Showing 3,986 changed files with 575,560 additions and 0 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
23 changes: 23 additions & 0 deletions .codecov.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
codecov:
notify:
require_ci_to_pass: yes
# wait for unit and integration test builds.
after_n_builds: 2
strict_yaml_branch: main # only use the latest copy on main branch

coverage:
precision: 2
round: down
range: "80...100"
status:
project:
default:
enabled: yes
target: 85% # This needs to be updated to 90 or higher.
patch:
default:
enabled: yes
target: 95%

ignore:
- "*/**/third_party/**/*" # Ignore all 'third_party' directories and files within those directories recursively.
6 changes: 6 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# This file is documented at https://git-scm.com/docs/gitattributes.
# Linguist-specific attributes are documented at
# https://github.com/github/linguist.

go.sum linguist-generated=true

161 changes: 161 additions & 0 deletions .github/CODEOWNERS

Large diffs are not rendered by default.

33 changes: 33 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**Steps to reproduce**
If possible, provide a recipe for reproducing the error.

**What did you expect to see?**
A clear and concise description of what you expected to see.

**What did you see instead?**
A clear and concise description of what you saw instead.

**What version did you use?**
Version: (e.g., `v0.4.0`, `1eb551b`, etc)

**What config did you use?**
Config: (e.g. the yaml config file)

**Environment**
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

**Additional context**
Add any other context about the problem here.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: feature request
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/new_component.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: New component proposal
about: Suggest a new component for the project
title: 'New component: '
labels: new component
assignees: ''

---

## The purpose and use-cases of the new component
<!--
This information can be used later on to populate the README for the component. See an example overview [here](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awsecscontainermetricsreceiver#overview).
-->

## Example configuration for the component
<!--
This will be used later on when creating `config.go` and added to README as well. See this receiver as an [example](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jaegerreceiver#getting-started).
-->

## Telemetry data types supported
<!--
Any combination of traces, metrics and/or logs is valid here.
-->

## Sponsor (Optional)
<!--
A sponsor is an approver who will be in charge of being the official reviewer of the code. For vendor-specific components, it's good to have a volunteer sponsor. If you can't find one, we'll assign one in a round-robin fashion. For non-vendor components, having a sponsor means that your use case has been validated.
If there are no sponsors yet for the component, it's fine: use the issue as a means to try to find a sponsor for your component.
-->
28 changes: 28 additions & 0 deletions .github/auto_assign.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Set to true to add reviewers to pull requests
addReviewers: false

# Set to true to add assignees to pull requests
addAssignees: true

# Set to true to add assignees from different groups to pull requests
useAssigneeGroups: true

# A list of assignees, split into different groups, to be added to pull requests (GitHub user name)
assigneeGroups:
approvers_maintainers:
# Approvers
- Aneurysm9
- anuraaga
- dashpole
- djaglowski
- dmitryax
- mx-psi
- pmm-sumo
# Maintainers
- bogdandrutu
- codeboten
- jpkrohling

# A number of assignees added to the pull request
# Set 0 to add all the assignees (default: 0)
numberOfAssignees: 1
Loading

0 comments on commit a7921d3

Please sign in to comment.