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.
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.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
uncrustify.cmakewon't pick up this ref update on pre-existing checkouts.In
tools/codestyle/uncrustify.cmake:5-30, thefile(STRINGS),git fetch, andgit checkoutare all insideif(NOT EXISTS "${EXTDEPS_DIR}/buildtools/manifest.cmake"). When themuse_depsdirectory already exists from a prior build, the new hash is never read or fetched, so the uncrustify toolchain stays on the old revision. In contrast,SetupDependencies.cmakereads and fetches unconditionally, so the main dependencies update correctly — leading to a potential mismatch between the two.This is a pre-existing issue, but it directly affects whether this ref update takes effect for the uncrustify path. Consider moving the
fetch/checkoutoutside the existence check inuncrustify.cmaketo mirrorSetupDependencies.cmake's behavior.🤖 Prompt for AI Agents