Forum Discussion
Advocate IIIPipeline git folder has a different name to pipeline name in workspace
Hi,
This is something that is just really annoying.
If I have my workspace backed by git, why when I change the name of a pipeline does the name of the pipeline folder in the repo not update to the new name?
Its annoying that I have to resale as twice to get it the name i want.
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.
6 Replies
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.
Hi caseybks ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.Hi caseybks ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
caseybksHi Anonymous,
Thank you for your reply. Yes, we are using the options you have mentioned. I just find it really annoying 😄
Hi caseybks ,
This is currently expected behavior because Fabric/ADF Git integration uses the pipeline’s logical ID for the folder name.Hopefully this improves in the future, but for now the best path is to track updates or submit an idea in the Fabric Ideas portal as mentioned in previous reply.
When you rename the folder in Git, the items within that folder can be seen as a deletion and recreation from a git perspective. This can cause syncing issues with the Fabric source control.
