-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Rust getting started #6515
Fix Rust getting started #6515
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Also love the console output being better than the JSON object.
/fix:all |
You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13816746876 |
IMPORTANT: (RE-)RUN
|
/fix:all |
You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13826175163 |
IMPORTANT: (RE-)RUN
|
@cartermp Is the automation capable of fixing the merge conflicts it introduced? or is it expected that the contributor(me) will fix the conflict? |
@cijothomas I assume you didn't touch the pt/ja files? Can you rebase your PR, that often helps with a situation like that |
Co-authored-by: Tiffany Hrabusa <[email protected]>
Co-authored-by: opentelemetrybot <[email protected]> Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
…lemetry#6545) Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Fixed #6503 #4365 #5745
Modify the getting started to match the latest OTel Rust release (0.28)
It only shows tracing signal (as before).
Mostly copied from existing example in the repo : https://github.com/open-telemetry/opentelemetry-rust/tree/main/examples