Should I use forward or backward slashes in my scripts?

While Windows often accepts forward slashes, this skill mandates using backslashes for file paths in Windows tools to ensure maximum compatibility and stability.

Can this skill help with GitHub Actions?

Yes, it includes specific configurations for running database deployments on windows-latest runners using both Bash and PowerShell shells.

Why does Git Bash mangle my SqlPackage arguments?

Git Bash (MSYS2) automatically converts POSIX-style paths starting with a forward slash into Windows paths, which breaks command-line switches like /Action:Publish by turning them into file paths.

How do I disable path conversion for a single command?

Prefix your command with MSYS_NO_PATHCONV=1 to instruct the shell not to alter the arguments before passing them to the Windows executable.

Windows Git Bash Path Manager

Name: Windows Git Bash Path Manager
Author: JosiahSiegel

byJosiahSiegel

•

Database Management

Resolves path conversion conflicts between Windows and Git Bash for SSDT, SqlPackage, and DACPAC workflows.

About

This skill provides specialized guidance for developers using Git Bash on Windows to manage SQL Server Data Tools (SSDT) projects. It solves the common issue where Git Bash improperly converts POSIX paths into Windows arguments for native tools like SqlPackage and MSBuild, leading to execution errors. By offering shell detection scripts, environment variable configurations like MSYS_NO_PATHCONV, and cross-platform command syntax, it ensures reliable database deployment and build processes across different terminal environments and CI/CD pipelines.

Key Features

Configuration strategies for MSYS_NO_PATHCONV to prevent argument mangling
Automatic shell detection for Bash, MSYS2, and PowerShell environments
Cross-platform CI/CD snippets for GitHub Actions on Windows runners
Enforcement of mandatory backslash usage for native Windows file operations
Standardized path handling for DACPAC files and SQL project builds
7 GitHub stars

Use Cases

Setting up GitHub Actions workflows that use Windows-native database tools
Creating cross-platform shell scripts that detect Windows environments
Deploying DACPAC files using SqlPackage from a Git Bash terminal

About

Key Features

Configuration strategies for MSYS_NO_PATHCONV to prevent argument mangling
Automatic shell detection for Bash, MSYS2, and PowerShell environments
Cross-platform CI/CD snippets for GitHub Actions on Windows runners
Enforcement of mandatory backslash usage for native Windows file operations
Standardized path handling for DACPAC files and SQL project builds
7 GitHub stars

Use Cases

Setting up GitHub Actions workflows that use Windows-native database tools
Creating cross-platform shell scripts that detect Windows environments
Deploying DACPAC files using SqlPackage from a Git Bash terminal