Does git create a branch from master or dev?
Git creates branches from Master or Dev?
When we use Git to manage code, branching is a very important concept. Using branches can ensure the stability of the code while developing, and can also facilitate team collaboration. But when creating a branch, a very common question is: Should you create a new branch from the Master branch or the Dev branch?
In this article, we will explore this issue, understand which branch should be created from, and why.
First of all, we need to understand the role of the Master branch and the Dev branch. The Master branch is the main branch of Git and the most stable branch. Code on the Master branch should be deployable and should not contain any untested or incomplete features. This ensures the stability and security of the production environment.
The Dev branch, as the development branch of Git, is an environment used to develop new features or fix bugs. The code on the Dev branch may not necessarily be stable, but it should be fully functional and tested code. The Dev branch also facilitates team collaboration because each developer can create their own branch on it to perform relatively independent development work.
Next, let's consider which branch should serve as the basis for the new branch. Generally, we should create new branches from the Dev branch. This is because the new branch created from the Dev branch contains all the latest code and features, and these features have also been tested.
However, in some cases, it also makes sense to branch from the Master branch. For example, if we need to create a branch to fix a bug, we can create a new branch from the Master branch. This is because the branch where the bug is fixed should be built based on the code that has been released to the production environment, that is, the code on the Master branch.
Also, if we are not sure which branch to create a new branch from, we can consider creating a new branch from the latest shared branch (such as the latest merge request). This ensures that we build new branches based on the latest shared code, reducing the chance of merge conflicts.
In summary, creating a new branch from the Dev branch is a better choice. This way we can build new branches based on the latest testable code, ensuring that our code has the latest functionality and stability. However, in some cases, it also makes sense to create a new branch from the Master branch, such as when fixing a bug. If we are not sure which branch to create a new branch from, we can consider creating a new branch from the latest shared branch.
In short, when creating a new branch, we should carefully consider and choose the correct branch to create. This ensures our code has the latest functionality and stability, while also improving team collaboration and the security of our production environment.
The above is the detailed content of Does git create a branch from master or dev?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











To download projects locally via Git, follow these steps: Install Git. Navigate to the project directory. cloning the remote repository using the following command: git clone https://github.com/username/repository-name.git

Steps to update git code: Check out code: git clone https://github.com/username/repo.git Get the latest changes: git fetch merge changes: git merge origin/master push changes (optional): git push origin master

To view the Git repository address, perform the following steps: 1. Open the command line and navigate to the repository directory; 2. Run the "git remote -v" command; 3. View the repository name in the output and its corresponding address.

In order to securely connect to a remote Git server, an SSH key containing both public and private keys needs to be generated. The steps to generate an SSH key are as follows: Open the terminal and enter the command ssh-keygen -t rsa -b 4096. Select the key saving location. Enter a password phrase to protect the private key. Copy the public key to the remote server. Save the private key properly because it is the credentials for accessing the account.

Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions and supports local operations; GitHub provides online collaboration tools such as Issue tracking and PullRequest.

To fall back a Git commit, you can use the git reset --hard HEAD~N command, where N represents the number of commits to fallback. The detailed steps include: Determine the number of commits to be rolled back. Use the --hard option to force a fallback. Execute the command to fall back to the specified commit.

Resolve: When Git download speed is slow, you can take the following steps: Check the network connection and try to switch the connection method. Optimize Git configuration: Increase the POST buffer size (git config --global http.postBuffer 524288000), and reduce the low-speed limit (git config --global http.lowSpeedLimit 1000). Use a Git proxy (such as git-proxy or git-lfs-proxy). Try using a different Git client (such as Sourcetree or Github Desktop). Check for fire protection

Git Commit is a command that records file changes to a Git repository to save a snapshot of the current state of the project. How to use it is as follows: Add changes to the temporary storage area Write a concise and informative submission message to save and exit the submission message to complete the submission optionally: Add a signature for the submission Use git log to view the submission content
