windows-git-bash-compatibility

Resolve Git Bash path conversion issues in Azure Data Factory scripts.

51|10|Updated Oct 22, 2025

Search Tags:#ci/cd #adf #git bash #azure data factory #windows compatibility #path conversion

Ready to run

npx skills add https://github.com/JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: windows-git-bash-compatibility
Source: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/main/plugins/adf-master/skills/windows-git-bash-compatibility
Command: npx skills add https://github.com/JosiahSiegel/claude-plugin-marketplace --skill windows-git-bash-compatibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common challenges and path conversion issues encountered when developing Azure Data Factory (ADF) solutions on Windows using Git Bash, ensuring smoother CI/CD pipelines and script execution.

Core Features & Use Cases

Path Conversion Guidance: Understand and mitigate Git Bash's automatic path conversion behavior.
Scripting Solutions: Provides examples for disabling path conversion in npm, PowerShell, and Azure CLI commands.
Shell Detection: Offers patterns to detect different shell environments (Bash, Node.js, PowerShell) for robust scripting.
Use Case: When running npm run build commands in Git Bash for ADF deployments, you encounter errors due to incorrect path translations. This Skill provides the MSYS_NO_PATHCONV=1 export to fix the issue.

Quick Start

Use the windows-git-bash-compatibility skill to learn how to disable path conversion in Git Bash for Azure Data Factory npm build commands.

Frequently Asked Questions about windows-git-bash-compatibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Does this Windows Git Bash compatibility guidance apply to Azure Data Factory CI/CD pipelines?▼

Yes, this Windows Git Bash compatibility guidance applies directly to Azure Data Factory CI/CD pipelines, providing best practices and solutions to resolve path conversion issues across npm, PowerShell, and Azure CLI scripts.

How do I fix Git Bash path conversion errors in Azure Data Factory npm build commands?▼

To fix Git Bash path conversion errors in Azure Data Factory npm build commands, export the environment variable `MSYS_NO_PATHCONV=1` to disable automatic path translation and ensure correct script execution.

Why does Git Bash change file paths automatically during Azure Data Factory CI/CD deployments?▼

Git Bash changes file paths automatically during Azure Data Factory CI/CD deployments due to MSYS path conversion behavior, which translates Windows paths to Unix-style paths and causes script execution failures in npm, PowerShell, and Azure CLI.

How to disable path conversion in PowerShell and Azure CLI scripts running through Git Bash?▼

To disable path conversion in PowerShell and Azure CLI scripts running through Git Bash, apply shell detection patterns and set specific environment variables like `MSYS_NO_PATHCONV=1` to prevent automatic path translation during execution.

What is the best way to detect shell environments in Windows for Azure Data Factory scripting?▼

The best way to detect shell environments in Windows for Azure Data Factory scripting is to implement shell detection patterns that identify whether Bash, Node.js, or PowerShell is running, ensuring robust cross-platform script execution.

Does this Windows Git Bash compatibility guidance apply to Azure Data Factory CI/CD pipelines?▼