Hi @caseybks ,
This behavior is expected with Fabric/ADF Git integration :
The pipeline folder name in Git is determined by the pipeline’s unique logicalId at creation, not its display name.
Renaming a pipeline in the workspace only updates the displayName in pipeline-content.json and does not automatically change the Git folder name, similar to how some IDEs handle class renaming.
Possible workarounds -
Manual Rename in Git: After renaming in the workspace, manually update the pipeline folder name in your Git repository and adjust any references as needed.
Delete & Recreate: For consistent naming, export the pipeline definition, delete the original, and recreate it with the preferred name.
Use Display Name as Reference: Since the displayName in pipeline-content.json is always current, you can use it for reporting or automation instead of the folder name.
Scripted Refactor: Some teams use scripts to rename folders and update pipeline-content.json for consistency.
Currently, there is no built-in option to automatically sync pipeline folder names with display names after creation. If this feature is important to your workflow, you may consider submitting a request through the Fabric Ideas portal for future enhancements.
