style(pre-commit): remove unwanted lines (#683)

xmfcx · web-flow · commit 080252a50fe6 · 2025-07-23T14:46:16.000+03:00
Signed-off-by: M. Fatih Cırıt &lt;mfc@autoware.org&gt;
diff --git a/docs/contributing/coding-guidelines/ros-nodes/topic-message-handling/supp-intra-process-comm.md b/docs/contributing/coding-guidelines/ros-nodes/topic-message-handling/supp-intra-process-comm.md
@@ -48,21 +48,17 @@ Here is a snippet of [_ros2_subscription_examples/intra_process_talker_listener/
 Below is a line-by-line explanation of the above code.
 
 - `if (this->get_node_options().use_intra_process_comms()){`
-
   - The statement checks whether or not intra-process communication is enabled or not by using `NodeOptions`
 
 - `auto intra_process_sub = sub_->get_intra_process_waitable();`
-
   - The statement means to get an embodied object which performs intra-process communication
 
 - `if (intra_process_sub->is_ready(nullptr) == true) {`
-
   - The statement checks if a message has already been received through intra-process communication
   - The argument of `is_ready()` is of type `rcl_wait_set_t` type, but because the argument is not used within `is_ready()`, `nullptr` is used for the moment.
     - Using `nullptr` is currently a workaround, as it has no intent.
 
 - `std::shared_ptr<void> data = intra_process_sub->take_data();`
-
   - This statement means to obtain a topic message from subscriptions for intra-process communication.
   - `intra_process_sub->take_data()` does not return a boolean value indicating whether a message is received successfully or not, so it is necessary to check this by calling `is_ready()` beforehand
 
diff --git a/docs/datasets/index.md b/docs/datasets/index.md
@@ -32,12 +32,10 @@ The data contains data from the following sensors:
 
 - You can find the produced full point cloud map, corner feature point cloud map and
   surface feature point cloud map here:
-
   - [https://drive.google.com/drive/folders/1_jiQod4lO6-V2NDEr3d-M3XF_Nqmc0Xf?usp=drive_link](https://drive.google.com/drive/folders/1_jiQod4lO6-V2NDEr3d-M3XF_Nqmc0Xf?usp=drive_link)
   - Exported point clouds are exported via downsampling with 0.2 meters and 0.5 meters voxel grids.
 
 - You can find the ROS 2 bag which is collected simultaneously with the mapping data:
-
   - [https://drive.google.com/drive/folders/17zXiBeYlM90gQ5hV6EAWaoBTnNFoVPML?usp=drive_link](https://drive.google.com/drive/folders/17zXiBeYlM90gQ5hV6EAWaoBTnNFoVPML?usp=drive_link)
   - Due to the simultaneous data collection, we can assume that the point cloud maps and GNSS/INS
     data are the ground truth data for this rosbag.
@@ -79,29 +77,24 @@ Used drivers for sensors give output in default ROS 2 message types and their ow
 types for additional information. Following topics are the default ROS 2 message types:
 
 - `/applanix/lvx_client/imu_raw`
-
   - Gives the output of INS system in ENU. Due to the 9-axis IMU, `yaw` value demonstrates the
     heading value of the sensor.
 
 - `/applanix/lvx_client/twist_with_covariance`
-
   - Gives the twist output of the sensor.
 
 - `/applanix/lvx_client/odom`
-
   - Gives the position and orientation of the sensor from the starting point of the ROS 2 driver.
     Implemented with `GeographicLib::LocalCartesian`.
 
     **This topic is not related to the wheel odometry.**
 
 - `/applanix/lvx_client/gnss/fix`
-
   - Gives the latitude, longitude and height values of the sensors.
 
     **Ellipsoidal height of WGS84 ellipsoid is given as height value.**
 
 - `/pandar_points`
-
   - Gives the point cloud from the LiDAR sensor.
 
 ## Bus-ODD (Operational Design Domain) datasets
diff --git a/docs/design/autoware-architecture/vehicle/index.md b/docs/design/autoware-architecture/vehicle/index.md
@@ -35,7 +35,6 @@ Each component contains static nodes of Autoware, while each module can be dynam
 The Vehicle Interface component can provide the following features in functionality and capability:
 
 - Basic functions
-
   - Converting Autoware control commands to vehicle specific command
   - Converting vehicle specific status information (velocity, steering) to Autoware status message
 
diff --git a/docs/how-to-guides/integrating-autoware/creating-maps/open-source-slam/fast-lio-slam/index.md b/docs/how-to-guides/integrating-autoware/creating-maps/open-source-slam/fast-lio-slam/index.md
@@ -80,7 +80,6 @@ sudo make install
 ## Other Examples
 
 - [Tutorial video 1](https://youtu.be/nu8j4yaBMnw) (using KAIST 03 sequence of [MulRan dataset](https://sites.google.com/view/mulran-pr/dataset))
-
   - Example result captures
     <p><img src="images/kaist03.png" width=712pix></p>
   - [download the KAIST 03 pcd map](https://www.dropbox.com/s/w599ozdg7h6215q/KAIST03.pcd?dl=0) made by FAST-LIO-SLAM, 500MB
diff --git a/docs/how-to-guides/integrating-autoware/creating-maps/open-source-slam/ia-lio-slam/index.md b/docs/how-to-guides/integrating-autoware/creating-maps/open-source-slam/ia-lio-slam/index.md
@@ -23,7 +23,6 @@
 ### Dependencies
 
 - [ROS](http://wiki.ros.org/ROS/Installation) (tested with Kinetic and Melodic)
-
   - `for ROS melodic:`
 
     ```bash
diff --git a/docs/how-to-guides/integrating-autoware/creating-vehicle-interface-package/vehicle-interface.md b/docs/how-to-guides/integrating-autoware/creating-vehicle-interface-package/vehicle-interface.md
@@ -6,7 +6,6 @@ The purpose of the vehicle interface package is to convert the control messages
 So, we can say that the purposes of the vehicle_interface are:
 
 1. Converting Autoware control commands to a vehicle-specific format. Example control commands of autoware:
-
    - lateral controls: steering tire angle, steering tire rotation rate
    - longitudinal controls: speed, acceleration, jerk
 
diff --git a/docs/how-to-guides/others/add-a-custom-ros-message.md b/docs/how-to-guides/others/add-a-custom-ros-message.md
@@ -5,11 +5,9 @@
 During the Autoware development, you will probably need to define your own messages. Read the following instructions before adding a custom message.
 
 1. Message in [autoware_msgs](https://github.com/autowarefoundation/autoware_msgs) define interfaces of `Autoware Core`.
-
    - If a contributor wishes to make changes or add new messages to `autoware_msgs`, they should first create a new discussion post under the [Design category](https://github.com/orgs/autowarefoundation/discussions/categories/design).
 
 2. Any other minor or proposal messages used for internal communication within a component(such as planning) should be defined in another repository.
-
    - [tier4_autoware_msgs](https://github.com/tier4/tier4_autoware_msgs) is an example of that.
 
 The following is a simple tutorial of adding a message package to `autoware_msgs`. For the general ROS 2 tutorial, see [Create custom msg and srv files](http://docs.ros.org/en/galactic/Tutorials/Beginner-Client-Libraries/Custom-ROS2-Interfaces.html).
diff --git a/docs/installation/autoware/source-installation.md b/docs/installation/autoware/source-installation.md
@@ -3,11 +3,9 @@
 ## Prerequisites
 
 - OS
-
   - [Ubuntu 22.04](https://releases.ubuntu.com/22.04/)
 
 - ROS
-
   - ROS 2 Humble
 
   For ROS 2 system dependencies, refer to [REP-2000](https://www.ros.org/reps/rep-2000.html).
@@ -154,7 +152,6 @@ sudo apt-get -y install git
    ```
 
    For Git users:
-
    - `vcs import` is similar to `git checkout`.
      - Note that it doesn't pull from the remote.
    - `vcs pull` is similar to `git pull`.
diff --git a/docs/reference-hw/index.md b/docs/reference-hw/index.md
@@ -9,14 +9,12 @@ The listed sensors and systems are not sold, developed or given direct technical
 The documents consists of the sections listed below:
 
 - AD COMPUTERs
-
   - ADLINK In-Vehicle Computers
   - NXP In-Vehicle Computers
   - Neousys In-Vehicle Computers
   - Crystal Rugged In-Vehicle Computers
 
 - LiDARs
-
   - Velodyne 3D LiDAR Sensors
   - Robosense 3D LiDAR Sensors
   - HESAI 3D LiDAR Sensors
@@ -25,25 +23,21 @@ The documents consists of the sections listed below:
   - Ouster 3D LiDAR Sensors
 
 - RADARs
-
   - Smartmicro Automotive Radars
   - Aptiv Automotive Radars
   - Continental Engineering Radars
 
 - CAMERAs
-
   - FLIR Machine Vision Cameras
   - Lucid Vision Cameras
   - Allied Vision Cameras
   - Tier IV Cameras
   - Neousys Technology Cameras
 
 - Thermal CAMERAs
-
   - FLIR Thermal Automotive Dev. Kit
 
 - IMU, AHRS & GNSS/INS
-
   - NovAtel GNSS/INS Sensors
   - XSens GNSS/INS & IMU Sensors
   - SBG GNSS/INS & IMU Sensors
@@ -53,26 +47,22 @@ The documents consists of the sections listed below:
 
 - Vehicle Drive By Wire Suppliers
   <!-- cspell: ignore Paravan -->
-
   - Dataspeed DBW Solutions
   - AStuff Pacmod DBW Solutions
   - Schaeffler-Paravan Space Drive DBW Solutions
 
 - Vehicle Platform Suppliers
-
   - PIX MOVING Autonomous Vehicle Solutions
   - Autonomoustuff AV Solutions
   - NAVYA AV Solutions
 
 - Remote Drive
-
   - FORT ROBOTICS
   - LOGITECH
 
 - Full Drivers List
 
 - AD Sensor Kit Suppliers
-
   - LEO Drive AD Sensor Kit
   - TIER IV AD Kit
   - RoboSense AD Sensor Kit
diff --git a/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md b/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md
@@ -3,7 +3,6 @@
 ## Steps
 
 1. Download and unpack a sample map.
-
    - You can also download [the map](https://drive.google.com/file/d/1A-8BvYRX3DhSzkAnOcGWFw5T30xTlwZI/view?usp=sharing) manually.
 
    ```bash
@@ -12,7 +11,6 @@
    ```
 
 2. Download the sample rosbag files.
-
    - You can also download [the rosbag files](https://drive.google.com/file/d/1sU5wbxlXAfHIksuHjP3PyI2UVED8lZkP/view?usp=sharing) manually.
 
    ```bash
