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

  • Home
  • SEARCH
  • 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 9092863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T22:56:37+00:00 2026-06-16T22:56:37+00:00

I have two feature branches which cannot me merged into master yet. Now I

  • 0

I have two feature branches which cannot me merged into master yet. Now I need to work on a third feature which depends on two previous features. How could I work on that feature without requiring the branches to be merged on master and but keep them split, so they could be code-reviewed separately?

A more direct question: If I merge feature1 into feature2, I still can make a pull-request of feature1 and later of feature2?

  • 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-16T22:56:38+00:00Added an answer on June 16, 2026 at 10:56 pm

    On your first question, you could create a new branch for feature 3 and then merge the two branches into it.

    On your second question, yes you could merge feature 1 into feature 2 and then when you are ready, merge feature 1 into master and after that feature2.

    You would need to make sure you keep the branches up to date.

    • Make sure both feature 1 and feature 2 have the latest master merge.
    • Make sure feature 3 receives merges of feature 1 & feature 2 if they get further commits

    The other way you could manage this, and keep things a bit tidier is to create a staging branch and merge feature 1 and feature 2 into it and then create feature 3 off the staging branch and merge it back in when the work is finished. Then when you are ready merge the whole staging branch into master. It depends on your reasons for delaying the merge of feature 1 and feature 2 into master.

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

Sidebar

Related Questions

I have two branches off of master, each one for a different feature, and
I have two branches: master and dev I want to create a "feature branch"
I have two branches, master and feature . I finished working on feature ,
I have two feature branches: featureA and featureB. FeatureA is complete, but not merged
Let's say you have two public feature branches, feature1 and feature2 . The workflow
I have two branches, the main branch(black) and a feature branch(yellow). As you can
I have seen two different ways of merging local branches. git checkout master git
Working on a project with git, I have two feature branches, call them dev-a
I have two branches, master and feature1. I was working on feature1 when I
I have two repo's which I'd like to keep separate. One for development, branches

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.