Error when switching between branches

[Bhargava05]

When switching my fabric workspace between different git branches(azure devops); i see following error 

Are there any such reserved names that shouldnt be used or is it just a bug? I read somewhere to just disconnect the branch and connect back to resolve the issue, but what if an contributor is facing the issue?

[nilendraFabric · Accepted solution]

Avoid using system-reserved names like `main`, `dev`, `prod`, or `test` without additional identifiers.
• Recommended naming: Use prefixes or suffixes (e.g., `sales-dev`, `feature-123`) to avoid conflicts

Contributors may lack permissions to switch branches. Ensure they have:
• Admin/Member roles in the Fabric workspace.
• Contribute/Branch creation permissions in Azure DevOps.
• Temporary workaround: Elevate the user to Admin to test permissions

Disconnect the workspace from Git, then reconnect to resolve sync issues.

[nilendraFabric · Accepted solution]

Avoid using system-reserved names like `main`, `dev`, `prod`, or `test` without additional identifiers.
• Recommended naming: Use prefixes or suffixes (e.g., `sales-dev`, `feature-123`) to avoid conflicts

Contributors may lack permissions to switch branches. Ensure they have:
• Admin/Member roles in the Fabric workspace.
• Contribute/Branch creation permissions in Azure DevOps.
• Temporary workaround: Elevate the user to Admin to test permissions

Disconnect the workspace from Git, then reconnect to resolve sync issues.

[v-ssriganesh · Accepted solution]

Hello @Bhargava05,
Thank you for reaching out to the Microsoft Fabric Community Forum and thank you, @nilendraFabric, for the detailed and helpful response.

We appreciate you bringing this issue to our attention. Based on the @nilendraFabric input, it’s likely that the error occurs due to the use of system-reserved names like main, dev, prod, or test. To avoid this, consider using unique identifiers such as prefixes or suffixes (e.g: sales-dev, feature-123) for your branch or file names.

Additionally, contributors may encounter issues if they lack sufficient permissions. Please ensure they have Admin/Member roles in the Fabric workspace and Contribute/Branch creation permissions in Azure DevOps. As a temporary test, elevating a user to Admin can help verify permissions. If the problem persists, disconnecting the workspace from Git and reconnecting it should help resolve sync issues.

If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.