From 9df4bc2a9e049bfb5527e562e51a1c5d78e28dd1 Mon Sep 17 00:00:00 2001
From: Felix Exner <feex@universal-robots.com>
Date: Mon, 31 Mar 2025 13:39:51 +0200
Subject: [PATCH] Remove semi-binary testing builds from ci_status (#1321)

The builds have been removed in 077bac55d909a1759e54d16d222ce8ece3be882e

(cherry picked from commit 3cec8a0d75e5cab75e9b250ac46f2f4f40192e29)
---
 ci_status.md | 14 +-------------
 1 file changed, 1 insertion(+), 13 deletions(-)

diff --git a/ci_status.md b/ci_status.md
index e8cd551e7..9850c6e27 100644
--- a/ci_status.md
+++ b/ci_status.md
@@ -29,10 +29,6 @@ red pipeline there should be a corresponding issue labeled with [ci-failure](htt
          <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/humble-semi-binary-main.yml/badge.svg?event=schedule"
               alt="Humble Semi-Binary Main"/>
       </a> <br />
-      <a href="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/humble-semi-binary-testing.yml?query=event%3Aschedule++">
-         <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/humble-semi-binary-testing.yml/badge.svg?event=schedule"
-              alt="Humble Semi-Binary Testing"/>
-      </a>
     </td>
     <td> <!-- jazzy -->
       <a href="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/jazzy-binary-main.yml?query=branch%3Amain+">
@@ -47,10 +43,6 @@ red pipeline there should be a corresponding issue labeled with [ci-failure](htt
          <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/jazzy-semi-binary-main.yml/badge.svg?branch=main"
               alt="Jazzy Semi-Binary Main"/>
       </a> <br />
-      <a href="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/jazzy-semi-binary-testing.yml?query=branch%3Amain+">
-         <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/jazzy-semi-binary-testing.yml/badge.svg?branch=main"
-              alt="Jazzy Semi-Binary Testing"/>
-      </a>
     </td>
     <td> <!-- rolling -->
       <a href="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/rolling-binary-main.yml?query=branch%3Amain+">
@@ -65,10 +57,6 @@ red pipeline there should be a corresponding issue labeled with [ci-failure](htt
          <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/rolling-semi-binary-main.yml/badge.svg?branch=main"
               alt="Rolling Semi-Binary Main"/>
       </a> <br />
-      <a href="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/rolling-semi-binary-testing.yml?query=branch%3Amain+">
-         <img src="https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/workflows/rolling-semi-binary-testing.yml/badge.svg?branch=main"
-              alt="Rolling Semi-Binary Testing"/>
-      </a>
     </td>
   </tr>
   <tr>
@@ -103,7 +91,7 @@ red pipeline there should be a corresponding issue labeled with [ci-failure](htt
 
    Uses repos file: `src/Universal_Robots_ROS2_Driver/Universal_Robots_ROS2_Driver-not-released.<ros-distro>.repos`
 
-1. Semi-binary builds - against released core ROS packages (main and testing), but the immediate dependencies are pulled from source.
+1. Semi-binary builds - against released core ROS packages, but the immediate dependencies are pulled from source.
    Shows that local build with dependencies is possible and if this fails we can expect that after the next package sync we will not be able to build.
 
    Uses repos file: `src/Universal_Robots_ROS2_Driver/Universal_Robots_ROS2_Driver.repos`