microsoft / microsoft/fabric-cli
[FEATURE] fab git connect - Connect workspace to git
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 173
- Forks
- 63
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Description
Use Case / Problem
To allow for git creation of branch out workspace, enable git connect commands so connect a workspace to Azure DevOps code repo. This is possible in the UI, SDK and REST API however not in fabric-cli library.
https://learn.microsoft.com/en-us/rest/api/fabric/core/git/connect?tabs=HTTP
Proposed Solution
fab git connect "dev_workspace.Workspace/.branches/featureX" \
--remoteGitRepositoryUrl "https://dev.azure.com/myorg/myproject/_git/myrepo" \
--remoteGitBranch "main" \
--personalAccessToken "$AZURE_DEVOPS_PAT" \
--repositoryType "AzureDevOps"
Alternatives Considered
Currently possible in REST APIs it seems
Impact Assessment
- This would help me personally
- This would help my team/organization
- This would help the broader fabric-cli community
- This aligns with Microsoft Fabric roadmap items
Implementation Attestation
- I understand this feature should maintain backward compatibility with existing commands
- I confirm this feature request does not introduce performance regressions for existing workflows
- I acknowledge that new features must follow fabric-cli's established patterns and conventions
Implementation Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing fab git commands and their tests to identify the established command and authentication patterns, then review the linked Microsoft Fabric Git connect REST endpoint. Add a connect command supporting the options shown in the issue and verify that it connects an Azure DevOps repository without changing existing commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, git, python
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100