<h3 id="heading-git-commit-workflow">Git Commit Workflow</h3>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1691870100468/ad75e870-ce0e-4bf2-a72d-b7d68d776443.png" alt class="image--center mx-auto" /></p>
<h3 id="heading-demystifying-git-commit-commands">Demystifying Git Commit Commands</h3>
<ol>
<li>Unified Staging: Command to Stage All Changes Simultaneously</li>
</ol>
<pre><code class="lang-plaintext">&gt;&gt; git add .
</code></pre>
<ol>
<li>Deciphering Staging: Commands to Prepare Specific Files for Commit. Add Multiple Files by Separating with Spaces.</li>
</ol>
<pre><code class="lang-plaintext">&gt;&gt; git add file1 file2
</code></pre>
<ol>
<li>Sealing Changes: Command to Commit All Staged Modifications</li>
</ol>
<pre><code class="lang-plaintext">&gt;&gt; git commit
</code></pre>
<ol>
<li>Comprehensive Committing: Command to Record All Staged Changes with a Descriptive Commit Message</li>
</ol>
<pre><code class="lang-plaintext">&gt;&gt; git commit -m "&lt;commit message&gt;"
</code></pre>
<ol>
<li>Rectifying a Forgotten File: Employing the Following Command After a Commit to Include the Missing Changes</li>
</ol>
<pre><code class="lang-plaintext">&gt;&gt; git commit -m "&lt;commit message&gt;"
&gt;&gt; git add &lt;forgotten file&gt;
&gt;&gt; git commit --amend
</code></pre>
<h3 id="heading-basic-guidelines">Basic Guidelines</h3>
<ul>
<li><p>Commit early and often</p>
</li>
<li><p>Make commit atomic</p>
</li>
<li><p>Write a meaningful but concise commit message</p>
</li>
</ul>
<h3 id="heading-selective-tracking-ignoring-files-in-git">Selective Tracking: Ignoring Files in Git</h3>
<p>we can tell git which files and directories to ignore in a given repo. The common files we never want to commit are as follows</p>
<ul>
<li><p>Secret API key</p>
</li>
<li><p>OS files</p>
</li>
<li><p>Log files</p>
</li>
<li><p>Dependencies and Packages</p>
</li>
</ul>
<p>Generate a file named ".gitignore" at the repository's root directory. In this file, we can include patterns that specify which files and folders should be ignored by Git.</p>


### Git Commit Workflow

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1691870100468/ad75e870-ce0e-4bf2-a72d-b7d68d776443.png align="center")

### Demystifying Git Commit Commands

1. Unified Staging: Command to Stage All Changes Simultaneously
    

```plaintext
>> git add .
```

1. Deciphering Staging: Commands to Prepare Specific Files for Commit. Add Multiple Files by Separating with Spaces.
    

```plaintext
>> git add file1 file2 
```

1. Sealing Changes: Command to Commit All Staged Modifications
    

```plaintext
>> git commit
```

1. Comprehensive Committing: Command to Record All Staged Changes with a Descriptive Commit Message
    

```plaintext
>> git commit -m "<commit message>"
```

1. Rectifying a Forgotten File: Employing the Following Command After a Commit to Include the Missing Changes
    

```plaintext
>> git commit -m "<commit message>"
>> git add <forgotten file>
>> git commit --amend
```

### Basic Guidelines

* Commit early and often
    
* Make commit atomic
    
* Write a meaningful but concise commit message
    

### Selective Tracking: Ignoring Files in Git

we can tell git which files and directories to ignore in a given repo. The common files we never want to commit are as follows

* Secret API key
    
* OS files
    
* Log files
    
* Dependencies and Packages
    

Generate a file named ".gitignore" at the repository's root directory. In this file, we can include patterns that specify which files and folders should be ignored by Git.

Committing with Confidence

Committing with Confidence

Table of contents

Git Commit Workflow

Demystifying Git Commit Commands

Basic Guidelines

Selective Tracking: Ignoring Files in Git