<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: legacy Git integration has been removed from Notebook in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/101322#M40632</link>
    <description>&lt;P&gt;Integrating a Databricks notebook with a Git repository using a feature branch sounds like a clean workflow for version control. The step-by-step process makes it straightforward to collaborate and track changes effectively. It's great that Databricks has these Git integration features built-in, simplifying development workflows!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 07 Dec 2024 10:58:55 GMT</pubDate>
    <dc:creator>FierceSkirtsist</dc:creator>
    <dc:date>2024-12-07T10:58:55Z</dc:date>
    <item>
      <title>legacy Git integration has been removed from Notebook</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/60313#M31635</link>
      <description>&lt;P&gt;How to integrate a notebook saved in workspace folder with git repos with feature branch?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 13:37:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/60313#M31635</guid>
      <dc:creator>Eren_DE</dc:creator>
      <dc:date>2024-02-15T13:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: legacy Git integration has been removed from Notebook</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/101304#M40623</link>
      <description>&lt;P&gt;To integrate a notebook saved in a Databricks workspace folder with a Git repository using a feature branch, follow these steps:&lt;/P&gt;
&lt;P&gt;1) &lt;STRONG&gt;Clone the Git Repository:&lt;/STRONG&gt; In the Databricks workspace, navigate to the folder where you want to create the Git repository clone. Click the down arrow next to "Add" in the upper right of the workspace and select "Git folder" from the dropdown.In the "Create Git folder" dialog, provide the URL of the Git repository you want to clone, select the Git provider (e.g., GitHub, GitLab, Azure DevOps), and name the folder.Click "Create Git folder" to clone the repository into your workspace.&lt;BR /&gt;2) &lt;STRONG&gt;Create and Switch to a Feature Branch:&lt;/STRONG&gt; Access the Git dialog from the notebook or the Databricks Git folders browser.In the Git dialog, you can see the current working branch. To create a new branch, click the button to create a new branch. Name your feature branch and switch to it.1&lt;BR /&gt;3) &lt;STRONG&gt;Make Changes in the Notebook:&lt;/STRONG&gt; Open the notebook you want to work on from the cloned Git folder.Make the necessary changes and save the notebook.&lt;BR /&gt;4)&lt;STRONG&gt;Commit and Push Changes:&lt;/STRONG&gt; After making changes, access the Git dialog again. Add a commit message describing your changes.Click "Commit &amp;amp; Push" to push the changes to the remote Git repository on the feature branch.&lt;BR /&gt;5)&lt;STRONG&gt; Pull Changes from the Remote Repository:&lt;/STRONG&gt; To ensure your local branch is up-to-date with the remote repository, click "Pull" in the Git operations dialog. Resolve any merge conflicts if they arise.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.databricks.com/en/repos/git-operations-with-repos.html" target="_blank"&gt;https://docs.databricks.com/en/repos/git-operations-with-repos.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 07 Dec 2024 05:35:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/101304#M40623</guid>
      <dc:creator>Mounika_Tarigop</dc:creator>
      <dc:date>2024-12-07T05:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: legacy Git integration has been removed from Notebook</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/101322#M40632</link>
      <description>&lt;P&gt;Integrating a Databricks notebook with a Git repository using a feature branch sounds like a clean workflow for version control. The step-by-step process makes it straightforward to collaborate and track changes effectively. It's great that Databricks has these Git integration features built-in, simplifying development workflows!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 07 Dec 2024 10:58:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-git-integration-has-been-removed-from-notebook/m-p/101322#M40632</guid>
      <dc:creator>FierceSkirtsist</dc:creator>
      <dc:date>2024-12-07T10:58:55Z</dc:date>
    </item>
  </channel>
</rss>

