Skip to content

Update readme to better describe integration with upstream #220

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

Merged
merged 1 commit into from
Jul 24, 2025

Conversation

jbachorik
Copy link
Collaborator

No description provided.

@jbachorik jbachorik requested review from zhengyu123 and r1viollet May 29, 2025 09:58
Copy link

github-actions bot commented May 29, 2025

🔧 Report generated by pr-comment-cppcheck

CppCheck Report

Errors (2)

Warnings (8)

Style Violations (300)

@jbachorik jbachorik force-pushed the jb/readme_upstream branch 2 times, most recently from 5d6c2b8 to a286d7a Compare May 29, 2025 10:00
Copy link

github-actions bot commented May 29, 2025

🔧 Report generated by pr-comment-scanbuild

@jbachorik jbachorik force-pushed the jb/readme_upstream branch from a286d7a to 03d4403 Compare May 29, 2025 12:43
@jbachorik
Copy link
Collaborator Author

Gentle ping on this trivial doc change

Copy link
Collaborator

@r1viollet r1viollet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Though can we adjust the link at the top ? Just adding based on async-profiler and refer to section bellow for details.

@jbachorik jbachorik force-pushed the jb/readme_upstream branch from 03d4403 to a57e8ee Compare July 24, 2025 12:59
@jbachorik jbachorik merged commit ea198f1 into main Jul 24, 2025
95 checks passed
@jbachorik jbachorik deleted the jb/readme_upstream branch July 24, 2025 13:11
@github-actions github-actions bot added this to the 1.29.0 milestone Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants