ci: Use the manifest to treat this an an app

This should allow the action-zephyr-setup to be able to fetch
everything.

Signed-off-by: David Brown <[email protected]>

Author: d3zd3z

.github/workflows/build.yml

@@ -1,3 +1,6 @@
+# Copyright (c) 2024 Linaro LTD
+# SPDX-License-Identifier: Apache-2.0
+
 name: Build
 
 # Build the rust samples and tests using the current Zephyr.
@@ -30,6 +33,7 @@ jobs:
         uses: zephyrproject-rtos/action-zephyr-setup@v1
         with:
           app-path: zephyr-rust-lang
+          manifest-file-name: ci-manifest.yml
           toolchains: arm-zephyr-eabi
             # TODO: Also bring in riscv.
 

ci-manifest.yml

@@ -0,0 +1,22 @@
+# Copyright (c) 2021 Nordic Semiconductor ASA
+# SPDX-License-Identifier: Apache-2.0
+
+# Although this normally lives as a module, the local CI uses action-zephyr-setup which wants the
+# application to have a manifest.
+
+manifest:
+  remotes:
+    - name: zephyrproject-rtos
+      url-base: https://github.com/zephyrproject-rtos
+
+  projects:
+    - name: zephyr
+      remote: zephyrproject-rtos
+      revision: main
+      import:
+        # By using name-allowlist we can clone only the modules that are
+        # strictly needed by the application.
+        name-allowlist:
+          - cmsis      # required by the ARM port
+          - hal_nordic # required by the custom_plank board (Nordic based)
+          - hal_stm32  # required by the nucleo_f302r8 board (STM32 based)