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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T07:33:21+00:00 2026-06-17T07:33:21+00:00

git status gives me this: Your branch is behind ‘origin/network’ by 11 commits, and

  • 0

git status gives me this:

Your branch is behind ‘origin/network’ by 11 commits, and can be fast-forwarded.

This is because I reset to an earlier version (hoping to discard all I had done after).

However, if I try to push that version (or that version with some minor changes) this is not working.
I do not want the new stuff, I just want to start new with the old version I reverted to!

What do I do?

  • 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-17T07:33:22+00:00Added an answer on June 17, 2026 at 7:33 am

    Since you’ve already pushed the “future” code, you want to avoid rewriting history at all costs if you have other contributors. You would introduce pretty severe updating nightmares.

    If you know that nobody else has pulled the newest code, you can do the following to “recreate” the branch at a specific point. The following rewrites the history of your network branch.

    git reset --hard <commit-id>
    git push --force origin network
    

    If you don’t want to rewrite history (you should always avoid rewriting push-ed history), you can ‘revert’ the last 11 commits on the network branch.
    The following is done while on the HEAD of your network branch.

    git revert OLDER_COMMIT^..NEWER_COMMIT
    

    This effectively creates commits which ‘revert’ existing commits. Though where you might find yourself in trouble on this is if you merge this branch into another branch later and wanted to preserve your existing 11 commits for the merged branch.
    See: the answer for Revert Multiple git commits.

    You could also revert the 11 commits in one commit.

    # reset your network branch to be the same as the remote
    git reset --hard origin/network
    
    # Set your branch (soft) index to the commit point you want your branch state to have:
    git reset --soft <commit-id>
    
    # The index will change and the files will reflect a difference you can now commit:
    git commit -a
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

git status shows that I have 2 commits # On branch production # Your
this is what my git status ' result looks like: # On branch master
If I run 'git status' on my repo it gives: # On branch master
This is my git status: # On branch create-views-question # Changes not staged for
git status tells me that my branch and the one I started from on
I did this: git branch --track stats_page to create a separate branch to try
After git reset --hard , git status gives me files within the Changes not
If I run git status: # On branch new-media # Changes not staged for
This is my Git status. Because of some weird reason, master and task-e branches
Is it possible to have git status only show the modified files due, in

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.