DEV Community: Jesse Kenson

AN INTRODUCTION TO BASIC GIT WORKFLOW

Jesse Kenson — Sun, 18 Jan 2026 11:01:38 +0000

What is Git?

The textbook definition of Git is an open-source, distributed version control system.

Since this is a beginner-friendly article, I shall break this definition down further.

Open-source simply means anyone is allowed to freely use, modify, share and redistribute Git.

A distributed version control system means that the Git can be accessed from both the central server and the user's local machine.

for more info on DISTRIBUTED VERSION CONTROL SYSTEMS,CLICK HERE

In terms of functionality, Git allows developers to track changes in their source code, coordinate work on shared projects, and maintain a detailed history of every modification made over time.

Expectation...

By the end of this article, you should have a fair understanding of basic Git commands and their respective uses. You should also be able to apply the basic Git workflow which involves these 6 key commands: Status - Add - Commit - Push - Pull - Branch

Basic Git Workflow Commands

Understanding Git as a workflow rather than isolated commands makes it far easier for a new user. Mastering the sequence gives you a strong foundation for working confidently with Git in real-world projects.

1.Initialize
The workflow begins by creating a git repository. At this point, Git is active but no files are being tracked yet.

    git init
  #Initializes a new Git repository.

2.Download a project
Alternatively, you can download an existing project, in which case there is no need for initializing.

    git clone [URL]
  #Creates a local copy of a remote repository.

3.Status
Once the repository is initialised or downloaded, the next step is to understand what Git sees- whether files are untracked, which files are modified and which files are ready to be commit.

    git status
  #Displays the state of the working directory and staging area.

4.Add/Stage files to commit
Before saving changes/commiting, you must select what to include after creating and/or editing files.

    git add [file]
  #Stages a file for a commit.

5.Save changes
Once files have been staged, they can be permanently recorded in Git History.

    git commit -m "message"
  #Saves changes with a descriptive message.

6.Save to work Server
Local commits stay on your machine until you send them to a remote repository(Such as Github or GitLab).

    git push 
  #Sends local changes to a remote repository(Server).

7.Get latest From Server
Retrieves changes that other people may update in a remote repository by syncing the pushed files.

    git pull
  #Fetches and integrates changes from a remote repository.

8.Create and Switch to branch
Branches allow you to work on new features or experiments wihout affecting the main codebase.

    git branch 
  #Lists, creates, or deletes branches.

9.Merge Branches

    git merge [branch-name]
  #Combines a branch into the current branch.

10.See History
This command is used to visualise and understand the project. it can therefore be used at any point after commits exist.

    git log --online --graph 
  #See who changed what and when.

{Fun Fact;Git was created by a guy called Linus Torvalds in 2005 to manage the development of the Linux kernel.}

Final thoughts on Git.

Git is a versatile and powerful tool that increases the efficiency of software development projects and simplifies remote collaborations. We’ve explained the fundamentals of how Git works and the most common Git commands you need to know before using it.

If you've made it this far...

INTRODUCTION TO GIT AS A DISTRIBUTED VERSION CONTROL SYSTEM SYSTEM

Jesse Kenson — Sun, 18 Jan 2026 11:01:18 +0000

INTRODUCTION

In this article, we try to understand one of the fundamental features of Git which is its Distributed Version Control System.

Disclaimer
This article assumes a basic understanding of Git and its functionality. In case you want to refresh your memory on the same, here is a link to get you started AN INTRODUCTION TO BASIC GIT WORKFLOW

What is a Version Control System?

This is a software that tracks and manages changes to fies(like code) over time, creating a complete history that lets developers revert to earlier versions, compare updates, and collaborateefficiently without overwritting each others work

What is a Version Control System?

Key Version Control System Functions

-Change Tracking and History: The system maintains a complete long-term record of every modification made to every file. This includes who made the change, when it was made, and why (via commit messages).

-Branching and Merging: Developers can create independent "branches" to work on new features or bug fixes in isolation without affecting the stable main codebase. Once complete, these changes can be "merged" back into the main project.

-Conflict Resolution: When multiple contributors edit the same part of a file simultaneously, the VCS identifies these conflicting changes and provides tools to help resolve them in an orderly manner.

-Rollback and Reversion: If a bug or error is introduced, the system allows teams to "undo" changes and revert files or the entire project to a previously known stable state.

-Traceability and Auditing: Every change is linked to its author and purpose, which is essential for troubleshooting, root cause analysis, and compliance with industry regulations.

-Collaboration: A VCS provides a "single source of truth," allowing team members (often geographically distributed) to contribute to a shared codebase simultaneously without overwriting each other's work.

-Backup and Recovery: In distributed systems (like Git), every developer’s local machine contains a full copy of the repository and its history, serving as a redundant backup in case the central server fails.

-Automation Support: Modern VCS tools integrate with CI/CD pipelines to automate testing, building, and deployment whenever new code is committed.

What is a Distributed Version Control System(DVCS)?

A distributed Version Control simply means every developer working on a project within the system can do so on their own local machines.

All the files,all commit history, all branches and all versions can be accessed via local machines.

This differs from the older Centralized Version Control Systems which were only accessible via a central server online.

What is a Central Version Control System?

This systems basically had one master copy of the entire repository on one repository(a central server) and developers only accessed this by going online.

These systems were the standard for many years(especially 1990s-2000s), but distributed systems like Git largely took over because they solve key pain points

Which Key Features define DVCS as the more popular Version Control System?

Offline work
You can do most of the functions locally without internet access, hence suitable and cost-effective for various working environments.
Speed
Most operations are instantaneous (no waiting for server) as all it takes is to read or write on the local drive.
Resilience
If the online repository goes down, you still have the entire project history on the local machine.
Flexible workflows
Anyone can contribute while working independently by proposing via pull requests and tracking changes.This makes it better for open-source and distributed teams.
Branching is encouraged
You can have dozens of new features being created, bugs being fixed and new ideas being tried safely without penalty (unlike in centralized systems where branching was often avoided).

Selecting the Right Tools

Although Git is the best version control system available, you may improve your development process even more by choosing supplementary tools and platforms. The following are some essential resources for optimizing your version control workflows;

a. GitHub

GitHub is a leading platform for hosting Git repositories and provides a range of tools for collaboration, such as project management, pull requests, and code reviews. The vast ecosystem of GitHub encourages community involvement and makes it easier for it to integrate with well-known development methods.

b. GitLab

GitLab offers a complete DevOps platform that includes deployment automation, continuous integration, and version control. GitLab enables teams to produce high-quality software at scale by streamlining their development lifecycle and providing integrated CI/CD pipelines, issue management, and code quality monitoring

Conclusion

Git's distributed version control system makes it possible for engineers to work together easily, efficiently handle code changes, and preserve code integrity. Gaining proficiency with Git is crucial for navigating the intricacies of contemporary software development, regardless of whether you're starting a new project or joining one that already exists.

Alright, lets git outta here...

Luxdev Markdown Language Class

Jesse Kenson — Tue, 13 Jan 2026 11:02:31 +0000

How to write a Markdown language

This is the first markdown language the students have learned and they can now write an article on dev.to

The first thing that students have learned.

How to write a heading

Last but not least

She had told me that she loves tech and i responded that
I enjoy tech too.

Morning Class
Evening Class

Night Class

m = "caleb"

Here is where you find me; visit my github account