From 67cfe9b41abaa84351a3bb52048af7b9c68d24de Mon Sep 17 00:00:00 2001 From: Your Name Date: Mon, 18 May 2026 10:03:48 -0500 Subject: [PATCH 1/2] JCF: see what happens when there's an intentionally broken link using Andrew's new workflow --- .github/workflows/dunedaq-develop-cpp-ci.yml | 2 +- docs/README.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/dunedaq-develop-cpp-ci.yml b/.github/workflows/dunedaq-develop-cpp-ci.yml index 067fb7f..c6f4e2c 100644 --- a/.github/workflows/dunedaq-develop-cpp-ci.yml +++ b/.github/workflows/dunedaq-develop-cpp-ci.yml @@ -28,6 +28,6 @@ on: jobs: build_develop_dispatch: name: Build against the development release - uses: DUNE-DAQ/.github/.github/workflows/dunedaq-develop-cpp-ci.yml@develop + uses: DUNE-DAQ/.github/.github/workflows/dunedaq-develop-cpp-ci.yml@amogan/check_broken_links with: caller_event_name: ${{ github.event.inputs.caller_event_name || github.event_name }} \ No newline at end of file diff --git a/docs/README.md b/docs/README.md index 55e9a1d..f1eff4d 100644 --- a/docs/README.md +++ b/docs/README.md @@ -62,6 +62,8 @@ There is an asymmetry between `send` and `receive`, where `send` takes a `void*` ![Class Diagrams](https://github.com/DUNE-DAQ/ipm/raw/develop/docs/ipm.png) +[This link is intentionally broken](https://github.com/DUNE-DAQ/ipm/raw/develop/docs/does_not_exist.md) + ### ZeroMQ Configuration Variables Currently, `ZmqContext.hpp` has two environment variables used to configure ZeroMQ within each application: From d983f836b5baa158b0f7b216bff0dce2bddcc910 Mon Sep 17 00:00:00 2001 From: Your Name Date: Mon, 18 May 2026 10:06:42 -0500 Subject: [PATCH 2/2] JCF: meaningless commit to trigger a workflow --- docs/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/README.md b/docs/README.md index f1eff4d..6f79bf4 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,4 +1,7 @@ # ipm + +This line is to re-trigger the workflow + Inter-Process Messaging The IPM library provides the low-level library for for sending messages between DUNE DAQ processes. IPM deals with messages consisting of arrays of bytes: higher-level concepts such as object serialization/deserialization will be handled by other libraries and processes building on IPM.