Updates to new features and some refactoring.#6591
Draft
Updates to new features and some refactoring.#6591
Conversation
|
|
Contributor
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #6591 +/- ##
========================================
Coverage 81.13% 81.13%
========================================
Files 2614 2614
Lines 72703 72703
Branches 9412 9412
========================================
Hits 58984 58984
Misses 10249 10249
Partials 3470 3470 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
bxdxnn
reviewed
Apr 15, 2026
Co-authored-by: bxdxnn <267911624+bxdxnn@users.noreply.github.com>
Co-authored-by: bxdxnn <267911624+bxdxnn@users.noreply.github.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Content
Update the contribution guide when it comes to new features and enhancements.
Motivation and context
We're receiving a lot more PRs for new features due to vibe-coding. Even that is "cheap", the engineers of the core team still need to process the PRs. We want to make sure that the PRs are following the overall direction of the product. This also helps contributors to get confidence that what they start working on will be accepted or what's necessary to get the PR accepted.