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 734281
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T07:21:16+00:00 2026-05-14T07:21:16+00:00

I have a git repo which has a few branches – there’s the master

  • 0

I have a git repo which has a few branches – there’s the master branch, which is our stable working version, and then there is a development/staging branch which we’re doing new work in.

Unfortunately it would appear that without thinking I was a bit overzealous with rebasing and have pulled all of the staging code into Master over a period of time (about 80 commits… yes, I know, stupid, clumsy, poor code-man-ship etc….).

Due to this it makes it very hard for me to do minor fixes on the current version of our app (a rails application) and push out the changes without also pushing out the ‘staged’ new features which we don’t yet want to release.

I am wondering if it is possible to do the following:

  1. Determine the last ‘trunk’ commit
  2. Take all commits from that point onward and move them into a separate branch, more or less rolling back the changes
  3. Start using the branches like they were made for.

Unfortunately, though, I’m still continually learning about git, so I’m a bit confused about what to really do here.

By the way, commits have been pushed to a remote, but I don’t mind re-pushing with –force, I am the only one who pushes remote.

Thanks!

  • 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-05-14T07:21:17+00:00Added an answer on May 14, 2026 at 7:21 am

    There will be the issue of publication (meaning you will have to:

    • force push the new master to your remote
    • communicate with anyone having already pulled from that remote in order for them to reset their master to the remote one
      )

    if your situation is:

    m1-m2-m3-m4-s1-s2-s3-s4 (master,stage)
    

    that is, if your current master its actually also the current stage branch, a simple reset is in order (as knittl mentions in his answer)

    But if your situation is:

    m1-m2-m3-m4-s1-s2-s3-s4-m5-m6 (master)
                           \
                            -s5-s6 (stage)
    

    as in: “I have integrated stage into master, and then go on working on master!”
    , then a rebase –onto is in order:

    git checkout master
    git reset --HARD m4
    git rebase --onto master s4 m6
    

    you will get:

    m1-m2-m3-m4-m5'-m6' (master)
               \
                -s1-s2-s3-s4-s5-s6 (stage)
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have a git project which has quite a big history. Specifically, early in
I have a git repository with multiple branches. How can I know which branches
Say I have a git repository and I've been working on master, can I
I have a a remote git repo and a local clone. Let's say I
I have a git repository which tracks an svn repository. I cloned it using
I have a Git repository which contains a number of subdirectories. Now I have
I have a git directory which contains the a whole bunch of files and
I have a git repository with remote foo. foo is a web app, is
I have a Git repository I store random things in. Mostly random scripts, text
Is it possible to have 2 git repositories in one directory? I'd think not,

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.