Extract folder variables in deptry workflows

[Copilot]

The deptry workflow previously delegated to make deptry, obscuring which folders were being checked. This extracts SOURCE_FOLDER and MARIMO_FOLDER as explicit workflow variables, matching the pattern used by the marimo workflow.

Changes

• GitHub Actions: Extract folder paths and Python version from Makefile, run deptry explicitly on each folder
• GitLab CI: Same approach, consolidated into single script block for variable scope
• Documentation: Updated .gitlab/TESTING.md and .gitlab/README.md to reflect variable extraction

Implementation

# Extract configuration
SOURCE_FOLDER=$(make -s -f Makefile -f - <<< 'print: ; @echo $(or $(SOURCE_FOLDER),src)' print)
MARIMO_FOLDER=$(make -s -f Makefile -f - <<< 'print: ; @echo $(or $(MARIMO_FOLDER),marimo)' print)
PYTHON_VERSION=$(cat .python-version 2>/dev/null || echo "3.13")

# Run deptry explicitly
if [ -d "$SOURCE_FOLDER" ]; then
  uvx -p "$PYTHON_VERSION" deptry "$SOURCE_FOLDER"
fi

This provides better visibility in workflow logs and maintains consistency with other workflows that extract configuration variables.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Revisit the deptry job</issue_title>
<issue_description>Deptry could be made better by writing into variables in the relevant flows and then within deptry workflow apply deptry to the content of the variables</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Revisit the deptry job #617

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[tschm]

No!