From 576542e136c9ffd2553649c1410e97d0193feb63 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Francisco=20Mart=C3=ADn=20Rico?= Date: Sun, 19 Nov 2023 08:29:43 +0100 Subject: [PATCH] Transition branch master -> rolling MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Francisco Martín Rico --- .github/workflows/{master.yaml => rolling.yaml} | 6 +++--- README.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) rename .github/workflows/{master.yaml => rolling.yaml} (95%) diff --git a/.github/workflows/master.yaml b/.github/workflows/rolling.yaml similarity index 95% rename from .github/workflows/master.yaml rename to .github/workflows/rolling.yaml index 61cc30b..abf2ae2 100644 --- a/.github/workflows/master.yaml +++ b/.github/workflows/rolling.yaml @@ -1,12 +1,12 @@ -name: master +name: rolling on: pull_request: branches: - - master + - rolling push: branches: - - master + - rolling workflow_dispatch: schedule: - cron: '0 0 * * 0' diff --git a/README.md b/README.md index dd6302b..5306f57 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # cascade_lifecycle -[![master](https://github.com/fmrico/cascade_lifecycle/actions/workflows/master.yaml/badge.svg)](https://github.com/fmrico/cascade_lifecycle/actions/workflows/master.yaml) +[![rolling](https://github.com/fmrico/cascade_lifecycle/actions/workflows/rolling.yaml/badge.svg)](https://github.com/fmrico/cascade_lifecycle/actions/workflows/rolling.yaml) [![foxy-devel](https://github.com/fmrico/cascade_lifecycle/actions/workflows/foxy-devel.yaml/badge.svg)](https://github.com/fmrico/cascade_lifecycle/actions/workflows/foxy-devel.yaml) [![galactic-devel](https://github.com/fmrico/cascade_lifecycle/actions/workflows/galactic-devel.yaml/badge.svg)](https://github.com/fmrico/cascade_lifecycle/actions/workflows/galactic-devel.yaml) [![humble-devel](https://github.com/fmrico/cascade_lifecycle/actions/workflows/humble-devel.yaml/badge.svg)](https://github.com/fmrico/cascade_lifecycle/actions/workflows/humble-devel.yaml) @@ -9,7 +9,7 @@ [Managed nodes](https://design.ros2.org/articles/node_lifecycle.html) (or lifecycle nodes, LN) are an extremely useful concept in ROS2. It provides a mechanism to define states in a node so that its life cycle can be better controlled. -When an application is made up of multiple LNs, it is common to use a node to orchestrate the transitions of each one. This occurs, for example, in [Navigation2](https://github.com/ros-planning/navigation2/tree/master/nav2_lifecycle_manager) or in [ROS2 Planning System](https://github.com/IntelligentRoboticsLabs/ros2_planning_system/tree/master/plansys2_lifecycle_manager). +When an application is made up of multiple LNs, it is common to use a node to orchestrate the transitions of each one. This occurs, for example, in [Navigation2](https://github.com/ros-planning/navigation2/tree/master/nav2_lifecycle_manager) or in [ROS2 Planning System](https://github.com/IntelligentRoboticsLabs/ros2_planning_system/tree/rolling/plansys2_lifecycle). `cascade_lifecycle` provides a mechanism that can make managing LNs easier. This idea is based on my developments with [BICA](https://github.com/IntelligentRoboticsLabs/BICA/tree/ros2). This mechanism allows defining dependencies between LNs. When an LN A establishes an LN B as a dependency, when an A enters a state, B automatically enters this state. This allows creating configuration/activation/deactivation trees.