DEV Community: Ömer Faruk Ölünk

Git Status And Commit Commands

Ömer Faruk Ölünk — Thu, 02 Oct 2025 20:36:29 +0000

Hello everyone ! Welcome back

Today we will talk about two of the most commonly used Git command: git status and git commit . But before we dive into those, let’s quickly go over a few important terms that will make thins clear.

In my first blog,I explained what Git is — as you might remember , Git helps you track your code and any changes made to it. It also allows you to save (or commit) those changes to your local repository whenever you want.

When you are working with Git, there are 3 main areas you’ll be dealing with. Let’s start by understanding what each of them does :

Working Directory
This is the folder where your acutal project files live. You can think of it as your everyday workspace — the place where you creates new folders, add or delete files and make changes to your codes.

Staging Area

The staging area acts like a bridge between working directory and your local repository. When you make changes in your working directory, you can move them to the staging area using the git add command. Once the changes are in staging area, they are ready to be commited.

Local Repository

Finally we can have the local repository — this is where Git permanently stores your commit history. It’s created whe you run the git init command , and all your commits are saved inside the hiden .git folder

There’s also something called remote repository , which is basically like GitHub — but don’t worry we will talk more about that later .

So, to summarize:

. The working directory where you you create or edit your project files.

. The staging area is where you prepare your changes before committing them.

. The local repository is where all your commits are stored.

Now that we’ve got that covered, let’s move on to our main topic:

The git status Command
The git status command shows the current state of your repository.
In other words, it’s like asking Git:

“Hey Git, what’s going on with my project right now?”

It answers questions such as:

. Which files have been changed but not yet committed?

. Which files are new and untracked by Git?

. Which files are staged and ready to be committed?

This command is super helpful to keep track of what’s going on in your project before you commit anything.

Before talking about commits, we should mention git add.
This command moves your changes from the working directory to the staging area.

You can add specific files using: git add filename

Or, if you want to add all changes at once: git add .

The git commit Command
Once your files are in the staging area, you can use the git commit command to save them permanently in your local repository.
You can also include a short message describing what you’ve done:git commit -m “Added new project files”

This helps you (and your teammates) understand what each commit was about when you look back at your history.

That’s all for today!
These two commands — and the concepts we discussed before them — are fundamental to understanding how Git works.

Don’t worry if everything doesn’t fully click right now. As we go through more Git lessons, everything will start to make perfect sense.

That’s it from me for today — see you in the next post.
Bye for now! 👋

Git Config

Ömer Faruk Ölünk — Sun, 21 Sep 2025 07:47:29 +0000

Hey welcome back!
Today we are going to talk about the git config command.
The git config command is basically Git's settings tool.
In other words ,it helps you configure how Git works and set up things like your user information.

For example, let's say multiple people are working on the same project.
In that case, you'll need to set and save your own user information (like your name or email) so Git can keep track of who made which changes.
Now let's take a look at how a git config command is written, with a simple example

Let's say , I want to set my name and email information in Git.
I would need write the command like this:

git config - -global user.name "Faruk"
git config - -global user.email "omrfrk72004@xmail.com"

And thats it - this is how you set up your user information in Git.

By the way the **- -global part **means this setting will apply to all of your Git project on your computer. In this way, your teammates will be able to see that the changes in the project were made by you .

That's all for today. Thank you so much for your support, and I'll see you in the next lesson!

What is this thing they call GIT?

Ömer Faruk Ölünk — Sat, 20 Sep 2025 13:35:58 +0000

Hello everyone
This blog is my first blog ever :) . I hope, i can do it properly.
The topic i'll talk about today is Git , a very useful application that has been used a lot in recant years. By the way, I should say from the beginning that I’m also learning these topics while explaining them to you — so in a way, we’re learning together. Let's get started then.

Basically, Git is a system designed to let you work on a project either with a team or on your own. With this system, you can make changes to your project, manage updates easily, and even roll back any changes if needed. In other words, it lets you develop your project in a really flexible way. And since you’re often working with others, your teammates can see what you’ve done and collaborate on the project too. That’s one of the most useful things about GIT!.
Think of it like this: four people are cooking together. Everyone grabs their ingredients and starts making their dish. Want to tweak something? Go ahead. Changed your mind ? No problem you can undo it. At the and, you all put your dishes on a shared cart and enjoy them together. It's great way to save time and effort while making best meal—or in Git’s case, the best project!.

Now , let's take a look at the difference between Git and GitHub to wrap up for today. That way we'll have a good starting point for tomorrow's topics. Git is the system we just talk about. GitHub on the other hand , is where you share the projects you work on using that system.

To put it in a metaphor: imagine you're working on a project and want to track it theoretically at first. Every day, you jot down notes, keep track of changes and record your progress in a notebook. That notebook = Git.
And GitHub is like putting that notebook online or sharing it with others. In a way you can think of GitHub as a Google Drive made specifically for developers.

That’s it for today! I wanted to give you a quick overview of what Git is, what it’s used for, and the difference between Git and GitHub. Hopefully, I managed to explain everything clearly. If not… well, I guess I probably didn’t fully get it myself either hahaha!

See you all next time!