CI: Ignore "doc/*"

.github/workflows/test_builds.yml

@@ -9,6 +9,7 @@ on:
       - "LICENSE"
       - "**/*.png"
       - "demo/*"
+      - "doc/*"
 
   pull_request:
     branches: [ master ]

doc/getting-started.md

@@ -16,12 +16,12 @@
 
 Behavior Trees are composed of tasks that represent specific actions or decision-making rules. Tasks can be broadly categorized into two main types: control tasks and leaf tasks. Control tasks determine the execution flow within the tree. They include `BTSequence`, `BTSelector`, and `BTInvert`. Leaf tasks represent specific actions to perform, like moving or attacking, or conditions that need to be checked. The `BTTask` class provides the foundation for various building blocks of the Behavior Trees. BT tasks can share data with the help of `Blackboard`.
 
-> **Note:** To create your own actions, extend the `BTAction` class.
+> **🛈 Note:** To create your own actions, extend the `BTAction` class.
 
 The BehaviorTree is executed from the root task and follows the rules specified by the control tasks, all the way down to the leaf tasks, which represent the actual actions that the agent should perform or conditions that should be checked. Each task returns a status when it is executed. It can be `SUCCESS`, `RUNNING`, or `FAILURE`. These statuses determine how the tree progresses. They are defined in `BT.Status`.
 
 Behavior Trees handle conditional logic using condition tasks. These tasks check for specific conditions and return either `SUCCESS` or `FAILURE` based on the state of the agent or its environment (e.g., "IsLowOnHealth", "IsTargetInSight"). Conditions can be used together with `BTSequence` and `BTSelector` to craft your decision-making logic.
 
->**Note:** To create your own conditions, extend the `BTCondition` class.
+>**🛈 Note:** To create your own conditions, extend the `BTCondition` class.
 
 Check out the `BTTask` class documentation in the editor, which provides the foundation for various building blocks of Behavior Trees.