Results for “setup”
Small, practical examples. Search by task or narrow things down below.
List only volumes matching a label
Docker / Compose: A label filter avoids relying on broad name patterns.
Docker / Compose✓ Tested
List paths changed on a feature branch since its merge base
Git: A three-dot diff compares the branch tip with the common ancestor.
Git✓ Tested
List paths saved in the latest commit
Git: List paths saved in the latest commit inside the disposable repository created by the input setup.
Git✓ Tested
List release tags matching a pattern
Git: Use a tag pattern and version-aware sorting for release labels.
Git✓ Tested
List remote-tracking branches after a fetch
Git: Remote-tracking references describe the last fetched state rather than live remote state.
Git✓ Tested
List the paths with unresolved merge conflicts
Git: The U diff filter identifies unmerged entries without parsing human-readable status output.
Git✓ Tested
List tracked file paths
Git: List tracked file paths inside the disposable repository created by the input setup.
Git✓ Tested
List untracked files while honoring ignore rules
Git: Use others and exclude-standard together to respect repository and global ignore configuration.
Git✓ Tested
Load environment variables from a file
Docker / Compose: An env file supplies one KEY=value assignment per line.
Docker / Compose✓ Tested
Load service variables from an env file
Docker / Compose: env_file supplies runtime environment values.
Docker / Compose✓ Tested
Make a Compose service’s filesystem read-only
Docker / Compose: Make a Compose service’s filesystem read-only in a small Compose file.
Docker / Compose✓ Tested
Match one of several values
Use IN to avoid repeating equality conditions.
IN✓ Tested