<p>In the early days of the internet, the information on the web consisted of just static pages. When it became interactive people started generating web pages on the server, making them more dynamic in nature.&nbsp;</p>
<p>With the advent of new technologies and site generators, a new philosophy of serving web pages is making us think about static pages again.&nbsp;</p>
<p>This new philosophy or architecture is called JAMstack which stands for JavaScript, APIs and Markdown stack.</p>
<p>The whole idea of JAMstack is to serve websites as static pages, giving dynamic nature using JavaScript, and exchange data through APIs.&nbsp;</p>
<p>As a result, it makes the developer experience simpler, improves performance with greater scalability, and reduces the cost of maintenance.&nbsp;</p>
<p>There are many static site generators available these days viz., NextJS, Hugo, Gatsby, etc.&nbsp;</p>
<p>With the help of third-party tools or services, these static sites can be made more dynamic.&nbsp;</p>
<p>Creating and maintaining static sites is inexpensive but adding dynamic features is where one has to spend on third-party tools.</p>
<p>One essential service which almost every website needs is a contact form and handling contact forms on static sites can be done through third-party services as we don't maintain a full-fledged server to handle forms on static sites.</p>
<p>Some of the static site form handling services are FormSpree, FormKeep, GetForm etc. These third-party services come at a price and free tier services have limitations in data and the number of submissions.&nbsp;</p>
<p>But here is a solution that helps you to handle forms on static sites without the need for these third-party tools.&nbsp;</p>
<p>It is called <strong>FormEasy</strong> which is a FREE and open-source apps script library that helps you to receive forms on static sites with full control of your data.</p>
<p>Form spree is a quite popular service for handling forms on static websites and <a href="https://devapt.com/formeasy" target="_blank" rel="noopener">FormEasy</a> can be the best formspree alternative with all customizations you want.</p>
<p>Let's see how to set up this FormEasy apps script library to handle static site forms.</p>
<h2 style="text-align: center;">FormEasy setup</h2>
<p>In a few simple steps, forms on static sites can be handled using FormEasy library.&nbsp;</p>
<ol>
<li>Create an empty Google sheets file</li>
<li>Open the Apps Script file connected to it</li>
<li>Add the FormEasy library using ScriptID</li>
<li>Add <code>doPost</code> apps script function</li>
<li>Deploy the apps script code and get the Web app URL to make POST requests</li>
</ol>
<h3 id="create_empty_google_sheet">1. Create an empty Google sheets file</h3>
<p>Visit this <a href="https://docs.google.com/spreadsheets/u/0/" target="_blank" rel="noopener">link</a> to create a new blank Google sheets file.</p>
<p><img src="../images/formeasy/create-empty-google-sheet.png" alt="Create-empty-Google-sheets-file-formeasy" /></p>
<h3 id="open_apps_script_file">2. Open the Apps Script file</h3>
<p>After creating an empty Google sheet file(you can rename the file if you want to), go to <strong><em>Extensions</em></strong> in the menu bar and click <em><strong>Apps Script</strong>.</em></p>
<p>It opens up an apps script file connected with the Google sheet.&nbsp;</p>
<p><img src="../images/formeasy/open-apps-script.png" alt="Open-apps-script-in-google-sheets" /></p>
<h3 id="add_formeasy_library">3. Add the FormEasy library</h3>
<p>In the left bar of apps script file click <code>+</code> button beside Libraries and add the below Script ID and click <strong><em>Look up</em></strong> button.</p>
<table style="border-collapse: collapse; width: 100.006%;" border="1">
<tbody>
<tr>
<td style="width: 97.9764%;">
<blockquote>ScriptID: 1CAyzGbXdwMlko81SbJAjRp7ewxhyGKhDipDK4v8ZvlpYqrMAAzbFNccL</blockquote>
</td>
</tr>
</tbody>
</table>
<p><img src="../images/formeasy/add-formeasy-library.png" alt="Add-FormEasy-library-to-apps-script" /></p>
<p>You will see two options <em>Version </em>and <em>Identifier</em>.&nbsp;</p>
<p>Select the latest version to reflect the latest changes made to the library if any or you can select the specific version as per the features you want.</p>
<p>For the identifier, the default name is <em>FormEasy</em> it is the name of the object used to call methods in the library. You can change it if you want but keeping it as it is can help you use the ready code snippets related to FormEasy.</p>
<h3 id="add_dopost_function">4. Add doPost function</h3>
<p>Clear the default functions if any in the default apps script file <em>Code.gs.</em></p>
<p>Create a function named <code>doPost</code>.&nbsp;</p>
<p><code>doPost</code> function name is the default name of the function that runs whenever a POST request is made to the script.</p>
<p>Next set the email if you want to get notified whenever any form gets submitted using <code>setEmail</code> method on FormEasy object. (FormEasy is the default identifier if you do not make any changes to the identifier while adding the FormEasy library)</p>
<p>Setting email is optional, the data gets logged in the Google sheet and you will not be notified through email if you do not set the email.</p>
<p>You need to return <code>action</code> method on FormEasy object with the <code>req</code> argument from the <strong><em>doPost</em></strong> function and this is the only mandatory method to use and all other methods on FormEasy are optional.&nbsp;</p>
<p><img src="../images/formeasy/add-formeasy-code.png" alt="Add-FormEasy-code" /></p>
<p>All the available methods on FormEasy library are:</p>
<div>
<ul>
<li><strong>setSheet</strong> - To select the specific sheet for saving the data(Default is active sheet)</li>
<li><strong>setEmail</strong> - To set the email for receiving notification</li>
<li><strong>setSubject </strong>- To set the subject of the email</li>
<li><strong>setFormHeading</strong> - To set the heading(inside email)</li>
<li><strong>setFields</strong> - To set the fields of the form(Lower case letters, also the keys of the JSON object)</li>
<li><strong>action</strong> - To return the response after submitting the form(Mandatory to return)</li>
</ul>
<p>The above all are optional methods except the <code>action</code>.</p>
<p>The simplest case looks like below:</p>
<pre class="language-javascript"><code>function doPost(req) {
  FormEasy.setEmail('youremail@domain.com'); // To receive email notification(optional)
  return FormEasy.action(req); // Mandatory to return action method
}</code></pre>
</div>
<h3 id="deploy_apps_script">5. Deploy the apps script code</h3>
<p>After saving all the changes to the code, it has to be deployed to use it.&nbsp;</p>
<p>To deploy, click the <strong>Deploy</strong> button at the top right corner and select&nbsp;<strong>New deployment</strong>&nbsp;and select type to&nbsp;<strong>Web app</strong>&nbsp;from the gear icon.</p>
<p dir="auto">Select/fill the below options</p>
<ul dir="auto">
<li>Description(optional),</li>
<li>Execute as&nbsp;<strong>Me(you email)</strong></li>
<li>Who has access&nbsp;<strong>Anyone</strong></li>
</ul>
<p>Click the <em>Deploy</em>&nbsp;button(authorize the script if you haven't done it before) and you will get a URL under&nbsp;<strong>Web app</strong>, copy that and it is going to be the endpoint for submitting the POST requests.&nbsp;</p>
<p>That's it. Now you can submit forms on this endpoint and they get logged in the Google sheet you selected. If you had set email then you will be notified through email whenever any form submission happens.</p>
<p><img src="../images/formeasy/deploy-apps-script.png" alt="Deploy-apps-script-code" /></p>
<p>If you want to make any changes to the script, like changing the subject text, email etc, you can do so and save the script. And while redeploying it instead of selecting <em>New deployment</em>, this time you have to select <strong>Manage deployments</strong> and click the pencil icon, select the <strong>New version,</strong> and click the deploy button.&nbsp;</p>
<p>The changes will be get reflected when you make the POST requests after that.&nbsp;</p>
<p><strong>Note:</strong> Whenever you make a new deployment, the web app URL changes. But when you redeploy using <strong><em>Manage deployments</em>&nbsp;</strong>option the URL remains the same.</p>
<p>Here is how a sample POST request using JavaScript <code>fetch</code> looks like.</p>
<pre class="language-javascript"><code>const data = {
  name: 'John',
  email: 'john@domain.com',
  message: 'Receiving forms is easy and simple now!',
};

const url = 'https://script.google.com/macros/s/&lt;Deployment ID&gt;/exec';

fetch(url, {
  method: 'POST',
  headers: {
    'Content-Type': 'text/plain;charset=utf-8',
  },
  body: JSON.stringify(data),
})
  .then((res) =&gt; res.json())
  .then((data) =&gt; console.log('data', data))
  .catch((err) =&gt; console.log('err', err));</code></pre>
<p>If you want to follow all the above instructions in the form of a video you can check this demo video.</p>
<div class="flex justify-center"><iframe class=" rounded-xl overflow-hidden" title="Text to image chrome extension intro" src="https://www.youtube-nocookie.com/embed/0u75mtnhifM?rel=0" width="680" height="350" frameborder="0" allowfullscreen="allowfullscreen"></iframe></div>
<p>As said already FormEasy is an open-source FormSpree alternative. You can check the source code of this library, fork it, make changes, use it yourself or you can contribute your code to the <a href="https://github.com/Basharath/FormEasy" target="_blank" rel="noopener">FormEasy Github repo</a>.</p>
<p>Hope this is a good solution to handle contact forms on static websites for FREE. If you have or found any such useful solution for static sites then do share it with us.</p>

Here is the free and open source formspree alternative to handle contact forms on static websites.
You can have full control of your data. 

Free FormSpree alternative to handle forms on static sites

<p>YAML is a recursive acronym for <em>Yaml ain't markup language</em>. It is generally considered easier to read than more verbose XML or JSON serialization languages.</p>
<blockquote>
<p><strong>Serialization</strong> is the process of translating a data structure or object state into a format that can be stored or transmitted and reconstructed later.</p>
</blockquote>
<p><code>YAML</code> is most often used for configuration files of servers and software applications. YAML files have an extension of .yaml or .yml. <a href="https://yaml.org/faq.html" target="_blank" rel="noopener">Yaml official site</a> recommends using <code>.yaml</code> extension whenever possible.</p>
<p>YAML syntax has python like indentation with nesting for representing hierarchical data. YAML is a superset of JSON, so every JSON data is a valid YAML but not vice-versa.</p>
<p>A sample YAML file looks like below.</p>
<pre class="language-yaml"><code>---
name: John
age: 25
hobbies:
  - swimming
  - dancing
  - programming</code></pre>
<p>YAML is used for config files in <a href="https://devapt.com/dynamodb-nodejs-crud" target="_blank" rel="noopener">AWS</a>, Docker, etc.</p>
<h2 style="text-align: center;">YAML syntax</h2>
<h3>Comments</h3>
<p>Unlike JSON, YAML allows having comments in the file. These comments can be inserted using a number sign(<code>#</code>). &nbsp;If <code>#</code> characters appear inside a string, then they are considered number sign <code>#</code>&nbsp;literals.</p>
<pre class="language-yaml"><code># This is a comment in yaml
name: John</code></pre>
<h3>Strings and numbers</h3>
<p>YAML supports various kinds of data types strings, numbers, boolean, arrays or lists, etc. The key-value pairs are separated with a colon followed by a space.</p>
<pre class="language-yaml"><code># Object(key-value pairs)
project: XYZ
version: 2.0</code></pre>
<p>It's optional to wrap strings with single or double-quotes. If there are any special characters or punctuation marks like colon(<code>:</code>) or dashes(<code>-</code>) in the strings then wrapping with quotes is recommended.</p>
<p>Tab characters are not allowed in YAML only whitespaces have to be used for indentation.&nbsp;</p>
<h3>Booleans</h3>
<p>The allowed boolean values are <code>true/false</code>, <code>yes/no</code>, <code>on/off</code></p>
<pre class="language-yaml"><code># Boolean value property
isOpenSource: true # equivalents &rarr; yes or on</code></pre>
<h3>Nesting key-value pairs</h3>
<p>The nesting of the key-value pairs is done by indenting the key-value pairs in the next line after the colon.</p>
<pre class="language-yaml"><code># Nested object(key-value pairs)
details:
  name: Server config
  service: abc
  state: started</code></pre>
<h3>Arrays or lists</h3>
<p>An array sequence starts with a dash(<code>-</code>) followed by a space and the indentation separates from the parent.&nbsp;</p>
<pre class="language-yaml"><code># Array of values
technologies:
  - SQL
  - GO
  - Javascript</code></pre>
<p>An array of objects(key-value pairs) can be written similarly just by indenting each key-value pair in reference to the dash(<code>-</code>).</p>
<pre class="language-yaml"><code># Array of objects
collaborators:
  - name: John
    age: 25
  - name: James
    age: 26</code></pre>
<h3>Multiline strings</h3>
<p>A pipe(<code>|</code>) character at the beginning of the string is used to have a string with multi-lines preserved without having to use any escape characters.</p>
<pre class="language-yaml"><code># Multiline strings
summary: |
  This is the first line of the string.
  This is the second and line break is preserved.</code></pre>
<p>When a greater than character(<code>&gt;</code>) is used at the beginning of the string then the multi-lines get wrapped by stripping leading indentations and trailing white spaces. This is good for writing the readable lines of strings without the need to preserve the line breaks.</p>
<pre class="language-yaml"><code># Folded text
description: &gt;
  This is a very very long text just wrapped
  in multi-lines but all this text is considered
  as a continuous text without any line breaks.</code></pre>
<h3>Document separator</h3>
<p>YAML allows having multiple documents in a single file by separating them with three hyphens(<code>---</code>).</p>
<pre class="language-yaml"><code>---
# A yaml document
project: XYZ</code></pre>
<h2 style="text-align: center;">YAML vs JSON</h2>
<p>The main aim of YAML is to make the data easily readable and understandable. Some of the major differences between YAML and JSON are:</p>
<table style="border-collapse: collapse; width: 100.006%; border-style: solid;" border="1">
<tbody>
<tr style="height: 23.7976px;">
<th style="width: 48.0477%; text-align: center; height: 23.7976px; border-style: solid; border-width: 2px;">YAML</th>
<th style="width: 48.0477%; text-align: center; height: 23.7976px; border-style: solid; border-width: 2px;">JSON</th>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">1. Easy to read and understand</td>
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">1. A bit difficult to read and understand</td>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">2. Uses nested indentation for hierarchy</td>
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">2. Uses braces and brackets for hierarchy</td>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">3. Comments are allowed</td>
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">3. No comments are allowed</td>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">4. Wrapping strings with quotes is optional</td>
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">4. Must wrap strings with double quotes</td>
</tr>
<tr style="height: 47.5952px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 47.5952px; border-style: solid; border-width: 2px;">5. Multiple documents are allowed in a single file</td>
<td style="vertical-align: top; text-align: left; height: 47.5952px; border-style: solid; border-width: 2px;">5. Only one document per file</td>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">6. It's a superset of JSON</td>
<td style="width: 48.0477%; vertical-align: top; text-align: left; height: 23.7976px; border-style: solid; border-width: 2px;">6. Every JSON is a valid YAML</td>
</tr>
<tr style="height: 23.7976px;">
<td style="width: 48.0477%; vertical-align: top; height: 23.7976px; border-style: solid; border-width: 2px;">7. Mostly used for configuration files</td>
<td style="width: 48.0477%; vertical-align: top; height: 23.7976px; border-style: solid; border-width: 2px;">7. Mostly used for transmitting data</td>
</tr>
<tr>
<td style="width: 48.0477%; vertical-align: top; border-style: solid; border-width: 2px;">8. Python developers like this format</td>
<td style="width: 48.0477%; vertical-align: top; border-style: solid; border-width: 2px;">8. Javascript developers like this format</td>
</tr>
</tbody>
</table>
<p>Below is the similar kind of data represented in YAML and JSON formats.</p>
<h3>A typical YAML file</h3>
<pre class="language-yaml"><code>--- # YAML example
project: XYZ
version: 2.0
isOpenSource: true
technologies:
  - SQL
  - GO
  - Javascript
collaborators:
  - name: John
    age: 25
  - name: James
    age: 26
details:
  name: Server config
  service: abc
  state: started
summary: |
  This is the first line of the string.
  This is the second and line break is preserved.
description: &gt;
  This is a very very long text just wrapped
  in multi-lines but all this text is considered
  as a continuous text without any line breaks.</code></pre>
<h3>The equivalent JSON file&nbsp;</h3>
<pre class="language-json"><code>{
    "project": "XYZ",
    "version": 2,
    "isOpenSource": true,
    "technologies": [
        "SQL",
        "GO",
        "Javascript"
    ],
    "collaborators": [
        {
            "name": "John",
            "age": 25
        },
        {
            "name": "James",
            "age": 26
        }
    ],
    "details": {
        "name": "Server config",
        "service": "abc",
        "state": "started"
    },
    "summary": "This is the first line of the string.\nThis is the second and line break is preserved.\n",
    "description": "This is a very very long text just wrapped in multi-lines but all this text is considered as a continuous text without any line breaks\n"
}</code></pre>
<p>YAML also has a few more features like node anchors, references etc.&nbsp; But all the above-discussed features are the essential ones to know in YAML. There are YAML linting tools to validate the YAML files which you can use to validate your files.</p>
<p>That's all about YAML and its comparison with JSON.</p>

YAML is a human-readable serialization language similar to XML and JSON. Here are all you need to know about the YAML syntax and comparisons with JSON

Sample excerpt

What is YAML? Learn YAML syntax & yaml vs json differences

<p>Git is a well-known version control system used by the majority of developers and organizations.&nbsp;</p>
<p>While making commits to the git repository there might be some accidental commits involving unintended changes or deletion of files.&nbsp;</p>
<p>In such a case, we can easily undo commits or changes with the help of a few git commands. Undoing git commits can be done in various methods based on how we wanted to keep the git history.&nbsp;</p>
<p>In this article, we're going to see those different methods to git undo commits.&nbsp;</p>
<p>Before actually diving into it, let's initialize git and commit a few files, so that we can use that to look into various git reverting commands.</p>
<p>Go to your favorite command line tool and run the below commands. Make sure that you have installed git in your system.</p>
<pre class="language-bash"><code># In the folder where you want to have a git repo
&gt; git init
&gt; echo One &gt; one.txt; echo Two &gt; two.txt; echo Three &gt; three.txt;  # Creating three files
&gt; git add one.txt
&gt; git commit -m "Adds one.txt"
&gt; git add two.txt
&gt; git commit -m "Adds two.txt"
&gt; git add three.txt
&gt; git commit -m "Adds three.txt"
&gt; git log --online

bdb52f3 (HEAD -&gt; master) Adds three.txt
c387fcb Adds two.txt
e99f4bf Adds one.txt</code></pre>
<p>Let's make some changes to a file and commit it.</p>
<pre class="language-bash"><code># Making changes to one.txt
&gt; echo Edited one &gt; one.txt
&gt; git commit -am "Updates one.txt" # Adding and committing directly
&gt; git log --oneline

8b730e8 (HEAD -&gt; master) Updates one.txt
bdb52f3 Adds three.txt
c387fcb Adds two.txt
e99f4bf Adds one.txt</code></pre>
<p>Now let's see how to git undo the last commit.</p>
<h2 style="text-align: center;">4 ways to git undo last commit</h2>
<h3>1. Using git revert</h3>
<p><code>git revert</code> command does the same as it states, that is it reverts any committed changes. This git command reverts the specified commit and creates a new commit with the reverted changes.&nbsp;</p>
<p>This is the most preferred git command for undoing or reverting any commits because this doesn't delete or orphan any of the commits. In short, this command doesn't rewrite the git history.</p>
<p>Let's see how to undo the commit using <code>git revert</code> command</p>
<pre class="language-bash"><code># Undoing the last commit using git revert
&gt; git revert HEAD</code></pre>
<p>To revert the last commit, we can use HEAD as it points to the last commit or we can use the hash of the commit we want to undo. By running the above command opens the configured editor to change the default message and once you close the editor, the last commit gets reverted with a new commit having "Revert" prefix to the actual commit name.&nbsp;</p>
<p>To avoid the editor from opening you can use <code>--no-edit</code> flag. To avoid committing the changes you can use <code>-n</code> or <code>--no-commit</code> flag as a result the reverted changes will be added to the staging(index) area without committing it.</p>
<pre class="language-bash"><code># Reverting without opening the editor
&gt; git revert --no-edit HEAD

# Reverting without committing the reverted changes
&gt; git revert -n HEAD</code></pre>
<p>Now let's see another way to git undo last commit.</p>
<h3>2. Using git reset&nbsp;</h3>
<p>The git reset is a powerful command using which we can undo a series of previously committed changes. This command orphans the commits by resetting the head to a specified state.</p>
<p><code>git reset</code> takes the commit hash or reference from HEAD to which it is going to reset to. Once the git reset command is run, there won't be any latest commit logs up to the commit hash.</p>
<p>We can undo the last commit in three different forms with the <code>git reset</code> command. There are three flags that can be used with this command, --soft, --mixed(default), --hard.&nbsp;</p>
<p>On <code>--soft</code> reset, the commit gets removed and the changes get added to the staging area.&nbsp;</p>
<p>On <code>--mixed</code> reset(default), the commit gets removed and the changes get added to the local or working area.&nbsp;</p>
<p>On <code>--hard</code> reset, the commit gets removed and all the changes would be lost.&nbsp;</p>
<p>So based on your requirement you can pick the appropriate flag to undo the last commit.</p>
<pre class="language-bash"><code># Undoing the last commit using git reset
&gt; git reset HEAD^ # points to the commit before the last one

# To completely undo the commit
&gt; git reset --hard HEAD^</code></pre>
<p>Now let's see the third way to undo the last git commit.</p>
<h3>3. Using git restore</h3>
<p>The <code>git restore</code> command is used to restore files in the working directory from the index or from other commits. We can also restore files to the index from other commits.&nbsp;</p>
<p><code>git restore</code> will not remove the previous commit logs or messages, it just restores the files or the directories as before.</p>
<pre class="language-bash"><code># Restoring the working directory from index
&gt; git restore .          # .(dot) means complete directory</code></pre>
<p>The above command just restores everything from the last commit. But what we want is to restore the commit before the last commit.&nbsp;</p>
<p>To restore files from other commits, git restore has <code>--source</code> flag, using that we can restore the parent of the last commit i.e., HEAD~1.</p>
<pre class="language-bash"><code># Undoing the last commit using git restore
&gt; git restore --source=HEAD~1 .</code></pre>
<p>By running the above command, the working directory will be with changes as that of the last commit's parent. It's just like <code>git revert -n HEAD</code> result but all the changes will be in the working directory not in the staging area.&nbsp;</p>
<p>To restore the changes to the staging area just use the <code>--staged</code> flag.&nbsp;</p>
<p>So using <code>git restore</code> command you will have the flexibility to commit changes with any message unlike git revert default message and also you can restore files specifically instead of the whole directory.&nbsp;</p>
<p>And now let's see the fourth way to undo the last git commit.</p>
<h3>4. Using git rebase -i</h3>
<p>The <code>git rebase -i</code> is a very powerful command for rewriting the git history. This command is used for rewording, editing, picking, dropping, squashing, etc commits.&nbsp;</p>
<p>git rebase with interactive flag helps to drop the commits. The same feature we can use to undo the last commit.&nbsp;</p>
<p>To make changes to the commit using <code>rebase -i</code> we need to go(rebase) to the parent of that commit and then make any changes we want.</p>
<pre class="language-bash"><code># Undoing the last commit using git rebase
&gt; git rebase -i HEAD~1 # select d - drop from the menu and proceed
</code></pre>
<p>When you run the above command your default editor gets opened with a list of actions you can perform on the last commit, select <code>d</code> or <code>drop</code> option and proceed. That will remove the last commit from the git log.&nbsp;</p>
<p>And that is how you can undo last git commit using rebase -i.</p>
<h3>Points to note</h3>
<p><code>git revert</code> and <code>git restore</code> will not modify the git history or log. So when dealing with collaborative works, it's good to use git revert and git restore for undoing the commits. This will help to maintain a clear log of all actions.&nbsp;</p>
<p><code>git reset</code> and <code>git rebase -i</code> will remove the logs of the commits. You can prefer this when your commits are local but in collaborative cases, you should strictly avoid using these because by chance you may end up rewriting the history of other people's commits.&nbsp;</p>
<p>Those are all the methods one can use to undo git commits. Which method to use depends on the individuals and their work environment.&nbsp;</p>

Here are the 4 ways to git undo last commit in simple and easy steps. You can learn which git commands to use to undo commits effectively.