Core FeaturesLesson 5 of 10

Making and Committing Changes

2 min readGitHub for Designers

Now that you have a local repository, let's learn how to make changes and save them as commits. Each commit is a checkpoint you can return to later.

First, see what's changed in your repository:

Terminal

git status

This shows modified files, new files, and files ready to commit.

Before committing, you need to "stage" the changes you want to include:

Terminal

# Stage a specific file
git add filename.txt

# Stage all changed files
git add .

Now save your staged changes with a descriptive message:

Terminal

git commit -m "Add new button styles to navigation"

Writing Good Commit Messages

Good commit messages describe WHAT changed and WHY. Start with a verb: "Add", "Fix", "Update", "Remove". Keep the first line under 50 characters.

Upload your commits to GitHub so others can see them:

Terminal

git push

You can now track and share your changes!

Core FeaturesLesson 5 of 10

2 min readGitHub for Designers

Now that you have a local repository, let's learn how to make changes and save them as commits. Each commit is a checkpoint you can return to later.

First, see what's changed in your repository:

Terminal

git status

This shows modified files, new files, and files ready to commit.

Before committing, you need to "stage" the changes you want to include:

Terminal

# Stage a specific file
git add filename.txt

# Stage all changed files
git add .

Now save your staged changes with a descriptive message:

Terminal

git commit -m "Add new button styles to navigation"

Writing Good Commit Messages

Good commit messages describe WHAT changed and WHY. Start with a verb: "Add", "Fix", "Update", "Remove". Keep the first line under 50 characters.

Upload your commits to GitHub so others can see them:

Terminal

git push

You can now track and share your changes!