Logo

    Home

    Documentation

    Use Cases

    Training

    Applications

    Release Notes

    Commit Changes

    Commit Changes

    Context:

    1 Context

    🧠
    By committing, the changes we made in our workspace are permanently saved to our branch. To do this, we need to export the changes from B1 to Gitpod and then commit.

    2 Result

    image
    image

    3 Step by step guide

    1. Navigate to the section “Deliver” -> “Changed Objects”
    2. Click on “Export Changes”
    3. Go back to Gitpod on the “Source Control” tab
    4. Stage your changes by clicking in the + button next to the number of changed files (Under the Commit orange button)
      5. icon

      This will add the changed files to the commit

    5. Type in a message to identify your commit
    6. Click on “Commit” to create the commit
    7. Click on “Sync” and accept the popup

    4 Explanation

    icon
    By committing and pushing, the changes we make in our workspace are permanently recorded on our branch. This triggers a pre-build of our code in Gitpod, which significantly speeds up the spin-up of the next workspace. When we start a new workspace based on this branch, our committed changes are available here.

    5 Helpcenter Article

    Version Control

    Build.One provides version control through git. Thanks to this, developers can implement new features in their applications through branches. In these branches, several developments can be carried out in parallel and then merged into the same version.

    helpcenter.build.one

    image
    Logo