-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(ci): Backport .github information from main
- Loading branch information
Showing
20 changed files
with
921 additions
and
475 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,46 +1,35 @@ | ||
<!-- | ||
* New contributors are highly encouraged to read our | ||
[CONTRIBUTING](/CONTRIBUTING.md) documentation. | ||
* Both Contributor and Reviewer Checklists are available at https://github.com/DataDog/datadog-agent/blob/main/docs/dev/contributing.md#pull-requests. | ||
* Contributors are encouraged to read our [CONTRIBUTING](/CONTRIBUTING.md) documentation. | ||
* Both Contributor and Reviewer Checklists are available at https://datadoghq.dev/datadog-agent/guidelines/contributing/#pull-requests. | ||
* The pull request: | ||
* Should only fix one issue or add one feature at a time. | ||
* Must update the test suite for the relevant functionality. | ||
* Should pass all status checks before being reviewed or merged. | ||
* Commit titles should be prefixed with general area of pull request's change. | ||
* Please fill the below sections if possible with relevant information or links. | ||
--> | ||
### What does this PR do? | ||
|
||
<!-- | ||
* A brief description of the change being made with this pull request. | ||
* If the description here cannot be expressed in a succinct form, consider | ||
opening multiple pull requests instead of a single one. | ||
--> | ||
|
||
### Motivation | ||
|
||
### Describe how you validated your changes | ||
<!-- | ||
* What inspired you to submit this pull request? | ||
* Link any related GitHub issues or PRs here. | ||
Validate your changes before merge, ensuring that: | ||
* Your PR is tested by static / unit / integrations / e2e tests | ||
* Your PR description details which e2e tests cover your changes, if any | ||
* The PR description contains details of how you validated your changes. If you validated changes manually and not through automated tests, add context on why automated tests did not fit your changes validation. | ||
If you want additional validation by a second person, you can ask reviewers to do it. Describe how to set up an environment for manual tests in the PR description. Manual validation is expected to happen on every commit before merge. | ||
Any manual validation step should then map to an automated test. Manual validation should not substitute automation, minus exceptions not supported by test tooling yet. | ||
--> | ||
|
||
### Additional Notes | ||
### Possible Drawbacks / Trade-offs | ||
|
||
### Additional Notes | ||
<!-- | ||
* Anything else we should know when reviewing? | ||
* Include benchmarking information here whenever possible. | ||
* Include info about alternatives that were considered and why the proposed | ||
version was chosen. | ||
--> | ||
|
||
### Possible Drawbacks / Trade-offs | ||
|
||
<!-- | ||
* What are the possible side-effects or negative impacts of the code change? | ||
--> | ||
|
||
### Describe how to test/QA your changes | ||
|
||
<!-- | ||
* Write here in detail or link to detailed instructions on how this change can | ||
be tested/QAd/validated, including any environment setup. | ||
--> | ||
--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,15 @@ | ||
--- | ||
# add system-probe label to any changes done in network, security, eventmonitor or ebpf packages | ||
component/system-probe: | ||
- pkg/collector/corechecks/ebpf/** #ebpf-platform (oomkill and tcp_queue_length) | ||
- pkg/ebpf/** # ebpf-platform (ebpf_manager) | ||
- pkg/eventmonitor/** # cws (new event monitor component) | ||
- pkg/network/** # npm and usm | ||
- pkg/process/monitor/** # usm (process monitor) | ||
- pkg/security/** # cws | ||
- pkg/util/kernel/** # ebpf-platform | ||
- cmd/system-probe/** # ebpf_platform (system-probe executable) | ||
- tasks/system_probe.py # invoke tasks | ||
|
||
|
||
- changed-files: | ||
- any-glob-to-any-file: | ||
- pkg/collector/corechecks/ebpf/** #ebpf-platform (oomkill and tcp_queue_length) | ||
- pkg/collector/corechecks/servicediscovery/module/** # usm | ||
- pkg/ebpf/** # ebpf-platform (ebpf_manager) | ||
- pkg/eventmonitor/** # cws (new event monitor component) | ||
- pkg/network/** # npm and usm | ||
- pkg/process/monitor/** # usm (process monitor) | ||
- pkg/security/** # cws | ||
- pkg/util/kernel/** # ebpf-platform | ||
- cmd/system-probe/** # ebpf_platform (system-probe executable) | ||
- tasks/system_probe.py # invoke tasks |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.