> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/resources/ci-cd-for-fabric-plan.md).
# CI/CD for Fabric Plan
Use CI/CD (Continuous Integration and Continuous Deployment) to streamline the development and deploying Fabric Plan content across environments. Integrate planning artifacts into source control, validate changes, and deploy updates consistently from development to production while reducing manual effort and deployment errors.
Fabric Plan supports two key CI/CD capabilities: Git integration and deployment pipelines. These tools help manage Plan items across development, test, and production environments by allowing individual plan items to be deployed, or multiple items to be deployed at once.
### Configure Git integration
Fabric Plan integrates with source control at the workspace level. You can commit all planning items in a workspace to a Git branch and version multiple planning items through a single process. The workspace structure, including folders, is preserved in the Git repository. Fabric supports source control through GitHub and Azure DevOps. For more information, see [Fabric Git Integration](https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAzure%2Ccommit-to-git).
1. Open the Fabric workspace to integrate with a Git repository.
2. Go to **Workspace Settings** and select **Git integration**.
3. Select your source control provider: **Azure DevOps** or **GitHub**.
4. Enter the Azure DevOps or GitHub account and repository details.
{% tabs %}
{% tab title="Azure DevOps" %}
If your Git provider is Azure DevOps, select **Connect** to automatically sign in to the Azure Repos account registered to the Microsoft Entra user signed into Fabric.
To add another account, select **Add Account** and enter the following details:
* **Display name**: Enter a name to uniquely identify the account.
* **Azure DevOps URL:** Enter the Git repository URL.
* **Authentication method:** Select OAuth 2.0 or Service principal.
{% endtab %}
{% tab title="GitHub" %}
If your Git provider is Github, select **Add Account** and enter the following details:
* **Display name**: Enter a name to uniquely identify the account.
* **Personal access token:** Enter the [fine-grained token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token) or [classic token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) you create in GitHub.
* **Repository URL:** Enter the Git repository URL.
{% endtab %}
{% endtabs %}
5. Select **Connect**.
6. In the **Connect Git repository and branch** section, select an existing branch or create a new branch.
7. Select **Connect and Sync**.
8. Fabric displays the branch, sync status for each item, and the time of the last sync.
### Commit changes to the Git repository
When you make changes to an existing plan, delete, or create a new plan, you must commit them to the Git repository linked to that workspace. The status of modified items changes to *Uncommitted*.
1. Select the **Source control** option.
2. Select the **Changes** tab from the **Source control** side pane. This tab displays all the items you changed, with an icon indicating the status: **New**  , **Modified**  , **Conflict**  , or **Deleted**  .
3. Select the items to commit to the Git repository and add an optional commit message. Select **Commit**.
4. After the selected items are committed to the Git repository, they are removed from the list. The item status changes to *Synced,* and the status bar displays the latest commit.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.fabricplan.com/resources/ci-cd-for-fabric-plan.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
