Files
computer-playbook/scripts
kevinveenbirkenbachandClaude Opus 5.5 00340c6795 chore(comments): drop the narrative Exception comments of this branch
The comment rule allows parameter docs and nocheck directives only, so
the five Exception comments this branch added go. What they explained:

- cli/administration/roles/marker.py: O_NONBLOCK keeps a FIFO planted
  under the marker name from blocking the open; the fstat refuses it.
- cli/administration/roles/source.py: a git hook exports GIT_DIR,
  GIT_INDEX_FILE and friends, which would point the scratch repository at
  the core checkout; the askpass helpers and the detached session keep a
  fetch that needs credentials from prompting.
- roles/web-app-bluesky/files/login-broker/server.js: the account map
  lives in the broker's own volume, never in a Keycloak user attribute; a
  bluesky_* attribute write under LDAP federation in WRITABLE mode
  triggers a schema-violating sync push that breaks later OIDC logins.
- roles/web-app-yourls/files/php/upgrade_database.php: YOURLS reports
  bootstrap and upgrade errors with die(), which exits 0; only the
  shutdown handler turns them into a failure.
- scripts/tests/deploy/act/workflow.sh: act copies the checkout through
  .gitignore, which drops the pulled custom roles, so the job binds the
  checkout to keep them.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-29 09:25:55 +01:00
..
…
…
…

Script Collection

This directory contains automation scripts used across the project.

  • system/ contains host and system-facing helpers.

  • container/ contains helpers that run inside the local container.

  • github/ contains GitHub workflow helper scripts.

  • For the canonical Make target index, see make.md.

  • 🛠️ Organize operational helpers for development, CI, release, and maintenance

  • 🧭 Separate responsibilities into focused subdirectories with clear scope

  • 📚 Keep script-based workflows discoverable and easier to navigate

The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.