

It's a good idea to do this frequently to ensure that the branch in your workspace has the most recent changes. You use the Pull action to update your local branch with any changes that other members push into the remote branch. For this reason, you should update the remote branch with your changes frequently using the Commit and Push commands. If other team members are working on the same application extension you are, you might all be working off the same branch. They can also view the source code in the repository, including all branches, by opening Git in VB Studio. Your team members can clone the branch in their workspaces and view the changes. Once your changes are pushed to the remote branch they are available to everyone else in your project. All the changes that you've committed since your previous push are copied to the branch in the remote repository. You use the Push action from the Designer’s drop-down menu to copy changes in your branch in the local repository to the branch in the remote repository.These commit messages can help you later to identify which files were changed and why.

You can also add a commit message describing the reason you updated those files (for example, "Added new layout X for field Y"). This local branch is where you work on your application extension.Īs you make your changes, you frequently use the Commit action from the Designer’s drop-down menu to mark the changes in your local repository branch that you want to copy to the remote repository:ĭescription of the illustration designer-commit.png Your workspace will contain a branch (which might be new or might already exist), but no one else can see the changes you make to the branch in your workspace until you choose to make them visible. Branches are usually created from the main branch, but might also be created from a different branch. When you create a workspace (or one is created for you), you get a clone of the project’s Git repository and all its branches. Your project’s Git repository is also called the remote repository, while the clone in your workspace is called the local repository. In most cases, the trunk or main branch of your project’s Git repository is the source from which your artifacts (like an app extension) are built.

If you’re unfamiliar with Git commands, it may be helpful to review the relationship between your workspace, your project, and the Oracle Cloud Applications development environment.
