Results for “Test-Path”
Small, practical examples. Search by task or narrow things down below.
List branches already merged into the current branch
Git: The merged filter reports branches whose tips are reachable from HEAD.
Git✓ Tested
List files containing a match
Linux Commands: Use grep -l when only the matching filenames are needed.
Linux Commands✓ Tested
List files tracked by Git
Git: ls-files reads the index instead of listing every file in the working directory.
Git✓ Tested
List ignored untracked files
Git: Combine ignored with others so the result is specifically ignored working files.
Git✓ Tested
List local branches
Print branch names in sorted order.
branch✓ Tested
List matching files
Enumerate immediate text files and sort their names in C#.
C#✓ Tested
List modified tracked files
Git: List modified tracked files inside the disposable repository created by the input setup.
Git✓ Tested
List newly added staged files only
Git: Filter the cached diff by added status while leaving modified files out.
Git✓ Tested
List only staged filenames
Git: The cached diff compares the index with HEAD rather than comparing working files with the index.
Git✓ Tested
List regular files recursively in sorted order
C++: Collect relative paths before sorting because directory iteration order is unspecified.
C++✓ 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