Difficulty: Beginner
Estimated Time: 10 minutes

Building on the previous scenario here you'll learn how to view changes in your working directory and commit them to your repository. This environment has a Git repository with a committed file. In the working directory a change to the committed file exists and a uncommitted file.

In future scenarios we'll cover how you can undo changes and share commits with other people.

This exercise has demonstrated how you can view your changes and commit them to the repository. In the next scenario we'll investigate how to share these changes with other people.

This exercise has been added to your scrapbook where you can review the example and code you written at any point.

Scenario 2 - Committing Changes

Step 1 of 6

Step 1 - Git Status

As discussed in the previous scenario git status allows us to view the changes in the working directory and staging area compared to the repository.

Given the current repository running git status displays that a change has been made in our working directory to a previously committed file, committed.js, but has not yet been moved to the staging area.

This tab will not be visible to users and provides only information to help authors when creating content.

Creating Katacoda Scenarios

Thanks for creating Katacoda scenarios. This tab is designed to help you as an author have quick access the information you need when creating scenarios.

Here are some useful links to get you started.

Running Katacoda Workshops

If you are planning to use Katacoda for workshops, please contact [email protected] to arrange capacity.

Debugging Scenarios

Below is the response from any background scripts run or files uploaded. This stream can aid debugging scenarios.

If you still need assistance, please contact [email protected]