Work With Branches
By default a semantic model's Git repository has one default main branch. However, you can add more branches to the repository for development purposes.
Branching lets you work on different features and updates at any time without affecting the original source code. You can create branches for feature development work and for things like urgent product fixes.
Before you start working on a new feature or update major portions of the source code, it’s considered a good practice to create a local branch and commit your changes to the local branch. This way your changes don’t affect the original source code and are safe to test and review.
Oracle assumes that you understand the concepts of working with branches in Git repositories. See https://git-scm.com/doc to learn more about the Git branch workflow.
The Oracle Analytics Git pane contains tabs that correspond to Git's standard repository development functionality like push, pull, and merge. This table describes how to use each tab.
| Tab Name | Icon | Description |
|---|---|---|
| Status |  |
Use this tab to view a list of and manage your unstaged, staged, and committed changes. This tab also displays files with merge conflicts. You can stage and commit some or all changes. When you commit a change, it moves the change into the branch you're working on. |
| Pull |  |
Use this tab to pull the committed changes made by other developers on the remote branch into your local branch. You use pull to ensure that you're working with the latest code. |
| Push |  |
Use this tab to push your staged and committed changes to the remote branch. The changes you push to the remote branch are available to the other developers using the branch. |
| Merge |  |
Use this tab to merge the contents of the selected branch into your current branch and resolve any resulting conflicts. See Understand and Resolve Merge Conflicts. |
| Switch Branch |  |
Use this tab to change from one branch to another. To switch to a remote branch, you must first create a local branch from the remote branch. Use the Create Local Branch tab to create the required branch. The name of the branch you're working on is displayed in the Semantic Modeler heading. |
| Create Local Branch |  |
Use this tab to create a local branch from the branch that you select. You work on your local branch instead of working on another public branch. On your local branch, you make your unstaged, uncommitted changes. Other developers can't access and update this branch. Only you can update this branch. Remember that you must create a local branch from the remote branch before you can use the Switch Branch tab to switch to the remote branch. |
| Delete Branch |  |
Use this tab to select and delete your local branches after you've finished working on them. |
| Manage Git Profiles |  |
Use this tab to regenerate or copy profile keys, update a profile's Git user name and password, or delete a profile. See View and Manage Git Profiles. |