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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T09:07:44+00:00 2026-06-13T09:07:44+00:00

When I merged a topic branch into master I received this message. I also

  • 0

When I merged a topic branch into master I received this message. I also have a remote at bitbucket named origin and heroku is named dev (originally origin, but renamed).

Should I also have something saying how many commits behind origin/bitbucket is? Is this because the bitbucket (now origin) was not cloned? I suspect it has something to do with tracking branches but i’m not entirely sure what that means.

 mistakes|tags-2col ⇒ co master
 Switched to branch 'master'
 mistakes|master ⇒ gmerge tags-2col 
 Merge made by the 'recursive' strategy.
  app.rb                 |    2 ++
  views/new/all_tags.erb |   57 +++++++++++++++++++++++++++++++++---------------
  2 files changed, 41 insertions(+), 18 deletions(-)
 mistakes|master ⇒ gs
 # On branch master
 # Your branch is ahead of 'dev/master' by 2 commits.
 #
 nothing to commit (working directory clean)


 mistakes|master ⇒ git remote
 dev
 origin
  • 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-13T09:07:45+00:00Added an answer on June 13, 2026 at 9:07 am

    You should only see a message regarding master compared to its upstream branch.

    If master is tracking ‘dev/master‘, then you know how it stands compared to that remote branch.
    See “Git: which is the default configured remote for branch?“.

    You could setup a remote with multiple urls, but it doesn’t seem safe:
    See “Git status in regards to multiple remote repositories“.

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

Sidebar

Related Questions

I have merged master into my bugXY branch, and needed to merge a file.
I did something stupid and accidently merged a topic branch into my master branch
I merged the beta branch into the master branch. I pushed to origin. I
If I have created and pushed a topic branch that has been merged to
My current pattern is to merge topic branches into my main development branch once
I have recently merged together 5 of my stand-alone projects into one project to
I have merged multiple jpeg files into one single .bin file. ..... ......... while(true){
I have some 100 files to be merged from one branch to the other.
I have an issue when I try to rebase an upstream branch into a
When merging topic branch "B" into "A" using git merge , I get some

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.