Files
computer-playbook/scripts/meta/resolve
kevinveenbirkenbachandClaude Opus 5.5 9a8cc70dbf fix(ci): stop a change under tests/ from deploying every role
scripts/meta/resolve/diff/affected_roles.sh emits __ALL__ as soon as
one changed path outside roles/<role>/ is not a .md or .rst file. A
role fix that also adds its unit test under tests/unit/python/roles/
therefore deployed the whole matrix: PR #982 changed
roles/web-app-zammad/ plus
tests/unit/python/roles/web-app-zammad/files/test_search_allocation_precheck.py,
and its "Detect affected roles" job logged "Resolver output: __ALL__".

Paths under tests/ now join the .md/.rst skip-list. No role deploy
reads the top-level tests/ tree, and those suites run in their own
jobs whatever the whitelist says. A diff of only skipped paths keeps
falling back to __ALL__, as before. The same resolver feeds
effective_whitelist.sh, so the narrowing applies to every diff-driven
run.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-18 13:04:50 +02:00
..
…

Resolve Scripts

This directory contains scripts that resolve metadata and derived values used by the project.

  • 🧩 Derive runtime values from repository and workflow context
  • 🔍 Resolve identifiers, references, and computed inputs
  • 🗂️ Keep lookup and resolution logic grouped in one place

Examples in this folder and its subfolders:

  • baseline_remote.sh resolves the remote whose main CI diffs against
  • repository/name.sh resolves the concrete repository name once for callers
  • repository/owner.sh resolves the concrete repository owner once for callers
  • See pr/README.md for the Pull Request-specific resolvers.

The scope of this folder is value resolution. Build, release, and wait-oriented behavior should stay in their dedicated script directories.