You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No matter what content is modified, it will be labeled test native. Such as #10658, #10421. I think there are something wrong in PR #10653. I saw the rule format is belong to v5, Relevant docs is here. If we want to add test native label to any change to instrumentation/logback/logback-appender-10/library/**、instrumentation/jdbc/library/**、instrumentation/spring/**、smoke-tests-otel-starter/** within the source dir EXCEPT for the instrumentation/spring/**/javaagent/**
We should add a top-level key all. Relevant labeler rule using description is as following:
Steps to reproduce
Create a PR to modify document.
Expected behavior
Just add test native label to necessary modules modified.
Actual behavior
No matter what content is modified, it will be labeled test native.
Javaagent or library instrumentation version
latest
Environment
JDK: OS:
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
No matter what content is modified, it will be labeled test native. Such as #10658, #10421. I think there are something wrong in PR #10653. I saw the rule format is belong to v5, Relevant docs is here. If we want to add
test native
label to any change toinstrumentation/logback/logback-appender-10/library/**
、instrumentation/jdbc/library/**
、instrumentation/spring/**
、smoke-tests-otel-starter/**
within the source dir EXCEPT for theinstrumentation/spring/**/javaagent/**
We should add a top-level key
all
. Relevant labeler rule using description is as following:Steps to reproduce
Create a PR to modify document.
Expected behavior
Just add
test native
label to necessary modules modified.Actual behavior
No matter what content is modified, it will be labeled test native.
Javaagent or library instrumentation version
latest
Environment
JDK:
OS:
Additional context
No response
The text was updated successfully, but these errors were encountered: