Skip to Content

Work with Branches in GitHub and SAP Web IDE

Requires Customer/Partner License
Create branches in GitHub, switch branches and update application in a different branch in SAP Web IDE.
You will learn
  • How your collaborators can create branches in GitHub
  • How to switch to the other branch in SAP Web IDE
  • How to make changes and commit the changes to the other branch
SathyaBhatSathyaBhatOctober 4, 2020
Created by
SathyaBhat
June 29, 2016
Contributors
SathyaBhat

Prerequisites

  • IMPORTANT: This tutorial cannot be completed on a trial account

This tutorial is written from a collaborator’s point of view.

  • Step 1

    Go to https://account.hanatrial.ondemand.com and log into your SAP Cloud Platform cockpit.

  • Step 2

    To open SAP Web IDE, click the Services tab in the navigation bar, scroll down and click the SAP Web IDE tile to open the SAP Web IDE service page.

    Find SAP Web IDE

    Click Go to Service.

  • Step 3

    Create a branch to which you will make the changes, as follows.

    1. Select your project in the workspace.

    2. Open the Git pane on the right-hand side.

    3. Click the + icon next to the branch label to create a branch.

      Create a branch
    4. Give the branch a suitable name, and then click OK.

      Branch details

    The branch is created and the branch that you are working with is displayed in the Git pane.

    Branch created

    This creates a local branch, in SAP Web ID#E, but does not change the repository on GitHub.

  • Step 4

    Right-click your project in the workspace, then select Git > Create Remote Branch.

    Enter a name for the branch, like m1, and click Create.

    Create remote branch
  • Step 5

    Since this branch is dedicated to milestone m1, which has 2 issues to be targeted, you will implement the changes for each of these in separate commits.

    For issue#1 you will do changes in S3_PurchaseOrderDetails.view.xml to remove the OrderedByName entry.

    Notice that when you save the changes, the Git pane shows the file that was changed. To commit the changes to the repository, select the Stage checkbox, enter a change description, and then click Commit.

    GitHub will automatically close an issue if your commit message includes certain keywords once this change is merged into the master branch. You will see this in the next tutorial.

    Add change description

    Click Commit to commit changes to the local repository.

    Click Push and select Remote branch, then select the m1 branch to push the changes to GitHub.

    Push to GitHub remote branch
  • Step 6

    Now if you check the m1 branch on the GitHub organization repository, you will see that the push has been completed and the changes are seen on GitHub.

    Push to GitHub remote branch is successful
  • Step 7

    Similarly you can address other remaining issues targeted for m1 milestone and commit and push the changes.

Back to top