Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7726895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T05:19:30+00:00 2026-06-01T05:19:30+00:00

Imagine a git repository that is structured as follows: Main branch – development for

  • 0

Imagine a git repository that is structured as follows:

  • Main branch – development for the next major release is done here
  • Release branches – development on patches for releases is done here
  • Hotfix branches – hotfix branches are branched off from release branches to fix release bugs for patches.
Main    -------------------------------->
                  \
Release            o--------o
                       \   /
Hotfix                  o--

So hotfixes are developed off the Release branch, and in order to bring hotfixes into my Main branch, my previous pattern has been to use cherry pick merges. Now I’m questioning whether this is appropriate.

Would using regular merge to merge the Hotfix branch into the Main branch be more appropriate here? Are there any “gotchas” in either scenario?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T05:19:31+00:00Added an answer on June 1, 2026 at 5:19 am

    I’d rebase my hotfixes onto the release branch and once in a while merge in the release branch into main, so main get the fixes as well.

    Cherry picked commits should be avoided imo, since they produce extra commits with the same content as the commit you are cherry picking from. Cherry pick is very useful if you have e.g. accidentally commited a hotfix on main but want the fix on the release branch as well but you don’t want to do a full merge from main into release, since it might contain other stuff that you don’t want to release yet.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I imagine that I should write a git commit hook (post-merge?) that would look
Is it possible to check out subdirectories of a repository in Git? Imagine I
Imagine you homebrew a custom gui framework that doesn't use windows handles (compact framework,
Imagine that you have a simple site with only 2 pages: login.aspx and secret.aspx.
I'm still trying to understand the ramifications of rebase and rewriting Git history. Imagine
I recently used git svn branch to create a branch (in both Subversion and
Since a branch is more or less only a tag, that moves automatically to
I have a git repository consist of several git submodules. If I want to
Imagine I have a service that looks like this: public interface MyAccountService { boolean
What is the fastest path to restore a git repository after a file system

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.