Closed dustmop closed 3 months ago
/merge
:steam_locomotive: MergeQueue: waiting for PR to be ready
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove
command.
Use /merge -c
to cancel this operation!
[Fast Unit Tests Report]
On pipeline 38027524 (CI Visibility). The following jobs did not run any unit tests:
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main
is 24m.
Use /merge -c
to cancel this operation!
Run ID: 8d8c1c25-23cd-4941-a698-126820af716d Metrics dashboard Target profiles
Baseline: ddbc83ccd58e53fd370620254b5ad27b4de6f3a2 Comparison: 1b8563cf880e4d25e441f5a76c115541b60c61fd
Performance changes are noted in the perf column of each table:
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
What does this PR do?
Allow components to pass the linter if they're using multiple implementations without a "primary"
impl
folder.Motivation
The docs explicitly allow components to use "non-primary" implementations, such as "impl-a" and "impl-b", but the linter doesn't take this use case into account: https://datadoghq.dev/datadog-agent/components/creating-components/#file-hierarchy
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes