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
Hello, I'm reaching out on behalf of the AWS X-Ray team. We would like to request the addition of new labels to php-contrib repository: sampler: aws:xray, propagator: aws:xray, and id-generator: aws:xray. These labels would be used for PRs and issues pertaining to the X-Ray Sampler, X-Ray Propagator, and X-Ray ID Generator. Ideally, there would be automation that adds these labels to PRs touching X-Ray component code - we would be happy to help with this if some guidance was provided.
Our goal is to have labelling across open-telemetry repositories so that we can find PRs and issues related to the X-Ray components and give faster support to the OTEL community.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi @mxiamxia I've created those labels in both our main and contrib repos (since issues are only created in the main repo).
There is no automation, so yes I'd like some guidance there.
Hi @Annosha you are welcome to work on this. If you do find a good way to automatically label issues/PRs, the project would be interested in something that can be applied more generally than just to x-ray.
Hello, I'm reaching out on behalf of the AWS X-Ray team. We would like to request the addition of new labels to php-contrib repository:
sampler: aws:xray
,propagator: aws:xray
, andid-generator: aws:xray
. These labels would be used for PRs and issues pertaining to the X-Ray Sampler, X-Ray Propagator, and X-Ray ID Generator. Ideally, there would be automation that adds these labels to PRs touching X-Ray component code - we would be happy to help with this if some guidance was provided.Our goal is to have labelling across open-telemetry repositories so that we can find PRs and issues related to the X-Ray components and give faster support to the OTEL community.
Thank you.
The text was updated successfully, but these errors were encountered: