Committing a Microsoft Fabric Workspace to a Git Repository

Поділитися
Вставка
  • Опубліковано 6 лип 2024
  • 4Microsoft Fabric supports connecting Fabric Workspaces with Git repositories. Watch this video to learn how to setup and use Git repos with Fabric. We'll cover configuration, synching notebooks and other content, as well as how to use Git to recover unintended changes to notebooks.
    This video is a demonstration of a related post at robkerr.ai/fabric-git-repo-co...
    0:00 Introduction
    0:50 Create a workspace
    1:55 Create a test notebook
    3:00 Create the Git Repo
    4:20 Connect the Repo to Fabric
    6:07 Commit a change to the Repo
    7:25 Recover an unintended change
    8:26 Summary
  • Наука та технологія

КОМЕНТАРІ • 8

  • @ioann.danylenko
    @ioann.danylenko 2 місяці тому

    Thank you for your work, Rob. I appreciate this video!

    • @robkerrai
      @robkerrai  2 місяці тому

      So glad it was helpful!

  • @skywalknotpossible
    @skywalknotpossible 4 місяці тому +1

    mate you have some really good content here. subscribed.

  • @vishnutelakapalli6080
    @vishnutelakapalli6080 2 місяці тому

    Hi Rob, The content was very useful, Do you have any complete tutorial to learn Fabric please. If already created please share the link. Thank you :)

    • @robkerrai
      @robkerrai  2 місяці тому

      I don't have a complete series. I'd recomed Will's series on his @LearnMicrosoftFabric channel www.youtube.com/@LearnMicrosoftFabric

  • @TheBas1202
    @TheBas1202 2 місяці тому

    Hi Rob, thanks for this video. How would you go about separate lakehouses for dev and prod, in relation to the notebook you sync?
    I tried doing exactly what you did here, but then in prod the notebook is trying to talk to the dev lakehouse.
    It seems the default lakehouse for the notebook is not put in git?

    • @robkerrai
      @robkerrai  2 місяці тому

      Microsoft's vision as presented at FabCon 24 was that different branches in a CI/CD environment are connected to different workspaces. The git features as I write this is pretty basic, but the design set out at FabCon is moving toward a more automated approach where creating a branch creates a workspace with all artifacts. In that scenario you probably would have a lakehouse in the Dev workspace, another lakehouse (with the same name) in a Prod lakehouse, etc.