I'm not sure I'm using the origin/upstream concepts how they should be used. I've forked a github repository to add some custom changes, set origin (at first push) to the fork in my personal github repo and set upstream (through b u) to the repo I forked (zenorocha in the following example).
Now whenever I commit to origin, magit-status indicates that I have some unpushed commits to upstream. I thought the purpose of the upstream branch was (at least in case of a fork) to give a default remote branch for fetching, but that it would not be used for pushing: that's what the origin branch is for. In my case I have no intention to push to the upstream branch, nor do I have write access to it. Is there some variable in magit to prevent it from reminding me that I have unpushed commits to the upstream remote branch ? Here is an example of the magit-status buffer. --8<---------------cut here---------------start------------->8--- Head: org-mode Back to bold, more flashy colors Merge: zenorocha/dracula-theme/master Release v1.2.0 Push: origin/org-mode Back to bold, more flashy colors Tag: v1.2.0 (3) Unpushed to zenorocha/dracula-theme/master (3) acfee96 org-mode origin/org-mode Back to bold, more flashy colors 6a2ca97 No bold/height, more colors bb158c5 origin/gnus-customization gnus-customization New faces for Gnus group/summary views --8<---------------cut here---------------end--------------->8--- Julien. -- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
