Add pre-commit and Update nav2 interface in rolling #4
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.
This pull request introduces a new
.pre-commit-config.yamlfile to standardize code formatting, linting, and quality checks using pre-commit hooks. Additionally, it cleans up several ROS message definition files by removing unnecessary trailing whitespace and blank lines, improving code readability and consistency.Add nav2_msgs and update nav_msgs in rolling.
Pre-commit automation:
.pre-commit-config.yamlto configure automated code quality checks, including formatting, linting, and spell checking for Python and ROS-related files.ROS message definition cleanup:
builtin_interfaces.ros,control_msgs.ros,controller_manager_msgs.ros, andlifecycle_msgs.rosto improve file cleanliness and maintainability. [1] [2] [3] [4]No functional changes:
gazebo_msgs.ros; only formatting was preserved.