> ## Documentation Index > Fetch the complete documentation index at: https://bruno-a6972042-docs-clustered-top-nav-v2.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Consumer Guide This guide covers Git operations for team members who clone and consume shared collections. Cloning, fetching, and pulling are available in the **free version** starting from Bruno 3.0.0. Choosing which remote and branch to pull from requires [Pro or Ultimate](https://www.usebruno.com/pricing). ## Cloning Collections from GitHub To clone a collection from GitHub into **Bruno**, you need to have an existing collection repository hosted on GitHub. For example, you can use this [Bruno repository](https://github.com/usebruno/github-rest-api-collection) and follow the steps below. 1. Launch **Bruno** and click the **Import Collection** button in the Quick Actions section on the Overview page. Alternatively, click the **+** icon in the sidebar and select **Import collection**. Import Option 2. In the Import Collection dialog, select the **Git Repository** tab. 3. Enter the **Git repository URL** and click the **Clone** button. Clone Repository 4. Choose a **Location** to clone the collection to. Choose Location 5. After the cloning process completes, select the **Collection** you want to open and click **Open**. Collection Open Your collection will now be open in **Bruno**. ## Checking for Updates You can check if there are new changes available in the remote repository. 1. Go to **Git UI**. 2. Click the **Fetch** button. 3. Bruno will display if there are incoming changes available. This allows you to see if your team has pushed new changes before you pull them. ## Pulling Changes Pull the latest changes from the remote repository to stay synchronized with your team. 1. Go to **Git UI** from top-right navbar icon. 2. Click the **Pull** button. 3. Bruno opens the **Pull from other branches** dialog and fetches your remotes and branches. 4. Select the branch you want to pull from. Your current branch is selected by default and is tagged **Current**. 5. If your collection has more than one remote, pick the one you want from the **Remote** dropdown above the branch list. 6. The note at the bottom of the dialog confirms where the changes will land, such as *Changes will be merged into main (current branch)*. 7. Click **Pull from selected branch**. Remote branches appear as `/` e.g. `origin/main`. Use the **Search branches...** box to filter longer lists. Pull from other branches Now you can see all your remote changes pulled in your collection. Picking a remote and a branch requires [Pro or Ultimate](https://www.usebruno.com/pricing). In the free version, **Pull** fetches and merges the branch your current branch already tracks, without opening the dialog. If you select a **local** branch other than the one you're on, Bruno switches to that branch before merging, so you don't have to check it out first. ### When a Pull Fails If the pull cannot complete, the dialog stays open and shows the Git output for the operation, and the primary button changes to **Close**. Close the dialog and click **Pull** again to retry. Retrying helps with transient failures such as a network timeout or a slow remote. For failures that need a fix first uncommitted local changes, or a branch that has diverged from the remote resolve the underlying issue before pulling again. If you have local uncommitted changes when pulling, you may be prompted to stash them first. The [Stash Changes](../using-gui/provider#stash-changes) feature (Pro/Ultimate) helps manage this workflow.