When dealing with large applications and with complex, CI/CD pipelines with multiple staging environments, it might be useful for you to have some way to automate applying the latest changes from one environment to the other. <h2 id="consistency-between-multiple-environments">Consistency between multiple environments</h2> At my work, we have three environments - one is the production environment (PROD), and two others are for fixing critical errors (HOTFIX) and developing new stuff (STAGING) with the possibility of introducing breaking changes. While creating a pull request with a quick fix of some bug and merging it to the HOTFIX environment (with future deployment to production), it is also necessary to have this code in the STAGING environment, so the future deployment of STAGING into PROD would not cause conflicts. The easiest way for having this cross-environment consistency is to make cherry-pick of the commit to STAGING after it is merged into HOTFIX. Easy, but manual, and since it&#39;s manual, someone can forget to do this. 😅 Plus, we need to know the specific identifier of a commit, so it&#39;s rather tricky for automatization. Another way to achieving this is to rebase STAGING on top of HOTFIX periodically. By doing it, we will have all of our feature changes as well as fixes of bugs. And also, it is somewhat manual work, but this time it is easy for automatization. For this automatization, we will use a <a href="https://github.com/steveukx/git-js">simple-git</a> library. <h2 id="a-lightweight-interface-for-running-git-commands">A lightweight interface for running git commands</h2> <a href="https://github.com/steveukx/git-js">Simple-git</a> is a tool for running git commands in any Node.js application. It gives us access to make all kinds of permutations on top of your commits and branches. With that library, we can easily create a script responsible for releasing our latest changes and running it from the command line. All we need to do in order to start using simple-git is to include into our JavaScript app and create a <code>git</code> instance: <pre><code class="lang-js">const simpleGit = require("simple-git");\nconst git = simpleGit.default(); </code></pre> Then, we have access to any git command as well as for options supported by that command. You can later visit the <a href="https://github.com/steveukx/git-js#api">public API of the library</a> to see the full list of available methods. For now, simply try to checkout on some test branch: <pre><code class="lang-js">await git.checkout("test-branch");\nconst branch = await git.branch();\n\n// logs "test-branch"\nconsole.log(branch.current)\n </code></pre> It works, and it&#39;s plain and simple like standard git commands! 🙂 <blockquote> Note: Remember that from within your script, any git command is like a side-effect, and it is not synchronous. </blockquote> Let&#39;s imagine having a script like one below, which executes all the commands needed for rebase one branch into another: <pre><code class="lang-js">async function main() {\n try {\n const status = await git.status();\n\n if (!status.isClean()) {\n return;\n }\n\n await git.checkout("HOTFIX");\n await git.reset("hard", ["origin/HOTFIX"]);\n await git.pull();\n\n await git.checkout("STAGING");\n await git.reset("hard", ["origin/STAGING"]);\n await git.pull();\n\n await git.rebase(["HOTFIX"]);\n await git.push("origin", "STAGING", ["--force"]);\n } catch (error) {\n const status = await git.status();\n\n if (status.conflicted.length &gt; 0) {\n return;\n }\n\n console.log(error);\n }\n } </code></pre> Our script fetches the latest changes on every branch, then it rebases STAGING branch on top of HOTFIX. Before executing anything, we check for not committed files since a hard reset will discard any changes made in development. Unfortunately in case of an error or merge conflicts, we must continue manually. So we have an automated way of rebasing branches to date with the latest HOTFIX environment. And with <a href="https://github.com/chalk/chalk">chalk</a>, we can make it a beautiful command-line script. Now with this script, which takes care of rebasing for us, the whole process of making your environments consistent is encapsulated in one single file, which can be executed from the command-line. <pre><code class="lang-js">node update-branches.js\n\n// or we can specify a command in package.json\nyarn update:branches\nnpm run update:branches\n </code></pre> I guess it is even possible to hook up this script in the deployment pipeline, for example, with <a href="https://github.com/features/actions">Github Actions</a> or <a href="https://github.com/typicode/husky">Husky</a>. I will explore this topic in the future. 😃 I really recommend you to inspect this awesome library for yourselves!