Parallel Development Made Seamless: Revolutionize Your Workflow with Git Worktree

GongSakura — Sun, 04 Jun 2023 11:24:56 +0000

In today’s fast-paced software development landscape, efficient collaboration and streamlined workflows are essential for teams to deliver high-quality code. Git, the widely adopted version control system, offers a range of powerful features to support these needs. One such feature is Git Worktree, a valuable tool that enables developers to manage multiple working trees within a single Git repository. In this article, we’ll explore what Git Worktree is and why it should be an integral part of your development toolkit.

What is git worktree?

Git Worktree is a feature introduced in Git 2.5 that allows you to have multiple working trees linked to the same Git repository. In simpler terms, it enables you to have multiple copies of your codebase in separate directories, each with its own branch, while still sharing the same underlying repository.

This means that you can work on different branches simultaneously without the need for complex branching strategies or repository clones.

Why we should use it?

There are several compelling reasons why Git Worktree is a valuable addition to your development workflow:

Seamless Branch Switching

Traditionally, switching branches involves either committing or stashing changes, switching to the desired branch, and then reapplying the changes.

With Git Worktree, you can have multiple working trees concurrently, allowing you to switch between branches without the need for committing or stashing changes, saving valuable time and minimizing disruptions to your workflow.

Parallel Development

Git Worktree empowers developers to work on multiple features or bug fixes simultaneously by creating separate working trees for each task.

This parallel development capability is especially beneficial for teams working on larger projects, enabling developers to isolate their changes and test them independently, without the risk of inadvertently affecting other ongoing work.

Lightweight and Efficient

Git Worktree offers an efficient way to work on different branches by utilizing the same repository objects, saving disk space and reducing the time required for cloning additional copies of the repository.

Rather than maintaining multiple complete copies of the project, Git Worktree shares the repository data, resulting in a lightweight setup that is both resource-friendly and convenient for developers.

Any git worktree manager recommands?

A powerful command-line tool @kanamara/wotkree is designed to automate Git worktree management.

Key features:

Seamlessly create and remove worktrees
Efficiently Manage Worktree Cleanup
Simple commands & Friendly prompts
Support multiple repositories

Few things you need to know about Promise Chain in Javascript

GongSakura — Sun, 25 Dec 2022 08:28:52 +0000

As we all know, one of the most significant features of promise is using the promise chain to replace the callback hell. That's awesome! And there are a few things you need to know about a promise chain to master it. Let's dive into it!

At the beginning, we define .then, and .finally are the primary promise chain methods. But why .catch is not accounted? As it is the same as .then(null, onRejected)

1. A pending promise can terminate the promise chain

A promise with pending state will not enter a promise chain and will not trigger any promise chain method.

// Example 1
// Created a pending promise simply by doing nothing.
const pendingPromise = new Promise(()=>{})

// the following code will not be executed
pendingPromise.then(
  ()=>{
    console.log('onFulfilled')
  },
  ()=>{
   console.log('onRejected')
  }
)

// Example 2
const fulfilledPromise = Promise.resolve('success')

fulfilledPromise.then(
  () => {
  // execute here
  console.log('trigger 1st then')
  // break the promise chain
  return new Promise(()=>{})
  },
).then(
  () => {
  // this will not be executed
  console.log('trigger 2nd then') 
  }
).finally(()=>{
  // this will not be executed
  console.log('trigger finally') 
})

2. After triggered .then, promise state will become fulfilled by default.

If we do not throw errors or return rejected promise during the promise chain, it will return fulfilled promise after triggered any promise chain method.

// Example 1
const rejectedPromise = Promise.reject('failed')
rejectedPromise.then(
  ()=>{
    console.log('onFulfilled, trigger 1st then ')
  },
  ()=>{
    // executed here
    console.log('onRejected, trigger 1st then')
  }
).then(
  ()=>{
    // executed here, as the promise state turned into fulfilled.
    console.log('onFulfilled, trigger 2nd then ')
  },
  ()=>{
    console.log('onRejected, trigger 2nd then ') 
  }
)

// Example 2
const fulfilledPromise = Promise.resolve('success')
fulfilledPromise.then(
  ()=>{
    // executed here
    console.log('onFulfilled, trigger 1st then ')
    throw new Error('failed')
  },
).catch(
  ()=>{
    // executed here, as the promise state turned into rejected
    console.log('onRejected, trigger catch') 
  }
).then(
  ()=>{
    // executed here, as the promise state turned into fulfilled.
    console.log('onFulfilled, trigger 2nd then ')
  },
  ()=>{
    console.log('onRejected, trigger 2nd then ') 
  }
)

3. .finally is not actually final

After triggered the .finally method, we can still trigger .then or .catch, and the promise state keeps unchanged that is different from .then method

// Example 1
const fulfilledPromise = Promise.resolve('success')
fulfilledPromise.then(
  ()=>{
   // execute here
   console.log('onFulfilled, trigger 1st then')
  }
).finally(()=>{
   // execute here
  console.log('trigger finally')
}).then(
  ()=>{
   // execute here
    console.log('onFulfilled, trigger 2nd then')
  }
)

// Example 2
const fulfilledPromise = Promise.resolve('success')
fulfilledPromise.then(
  ()=>{
   // execute here
   console.log('onFulfilled, trigger 1st then')
   throw new Error('failed')
  }
).finally(()=>{
   // execute here
  console.log('trigger finally')
}).then(
  ()=>{
    console.log('onFulfilled, trigger 2nd then')
  }
).catch(
  ()=>{
   // execute here
   console.log('onRejected, trigger catch')
  }
)

DEV Community: GongSakura