git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Marginean <alexmarginean16@gmail.com>
To: git@vger.kernel.org
Subject: BUG
Date: Wed, 4 Nov 2020 18:10:06 +0200	[thread overview]
Message-ID: <CALG6MqwdCmwS5D_F9+q6UYzGm5ZzLL7Bi=rD7Ph2XE0uccu+xg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Hey,

Github has changed the way they name branches, so now instead of the
`master` branch there is the `main` branch however, I'm having some
trouble with the naming

**Steps to replicate my problem**

1. Create a new Github repository and make sure the default branch is `main`
2. Add something to the repo, a `README.md` file should be enough
3. Instead of cloning the repo make a new directory with your repo's
name `mkdir <repo_name>` and change the directory to it `cd
<repo_name>`
4. `git init`
5. Add the remote repo with `git remote add origin <repo_link>`
6. Pull the `main` branch from the remote repo with `git pull origin main`.

After the step number 6. instead of my branch changing to `main` my
current branch is changed to `master` which has every file and change
of the branch `main`. This is a real problem because if I try to push
changes to `main` although my current branch shows up as `master` it
creates another branch called `master` on Github and the `main`
remains unchanged. Yeah sure I can `git checkout main` after that and
make my changes there but I'm not sure why it defaults to `master` and
copies `main` from Github into local branch `master`.

P.S. If you were to use `git fetch origin` instead of `git pull origin
<branch_name> and then manually change branch to `main` with `git
checkout main` it would work. Also, if you were to clone the Github
repo using `git clone <link>` you will get the correct current branch
that is `main`.

Sincerely,
Alex

[-- Attachment #2: git-bugreport-2020-11-04-1731.txt --]
[-- Type: text/plain, Size: 2639 bytes --]

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

Github has changed the way they name branches, so now instead of the `master` branch there is the `main` branch however, I'm having some trouble with the naming

1. Create a new Github repository and make sure the default branch is `main`
2. Add something to the repo, a `README.md` file should be enough
3. Instead of cloning the repo make a new directory with your repo's name `mkdir <repo_name>` and change the directory to it `cd <repo_name>`
4. `git init`
5. Add the remote repo with `git remote add origin <repo_link>`
6. Pull the `main` branch from the remote repo with `git pull origin main`.

What did you expect to happen? (Expected behavior)

After step 6. I expected to be switched to a branch called `main` that would include every file and change from the `main` branch on the origin. 

What happened instead? (Actual behavior)

After the step number 6. instead of my branch changing to `main` my current branch is changed to `master` which has every file and change of the branch `main`. This is a real problem because if I try to push changes to `main` although my current branch shows up as `master` it creates another branch called `master` on Github and the `main` remains unchanged. Yeah sure I can `git checkout main` after that and make my changes there but I'm not sure why it defaults to `master` and copies `main` from Github into local branch `master`.

What's different between what you expected and what actually happened?

The name of the branch and the duplication of the `main` branch to a branch called `master`.

Anything else you want to add:

P.S. If you were to use `git fetch origin` instead of `git pull origin <branch_name> and then manually change branch to `main` with `git checkout main` it would work. Also, if you were to clone the Github repo using `git clone <link>` you will get the correct current branch that is `main`.

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.29.2
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 x86_64
compiler info: clang: 12.0.0 (clang-1200.0.32.21)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh


[Enabled Hooks]
not run from a git repository - no hooks to show

             reply	other threads:[~2020-11-04 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 16:10 Alex Marginean [this message]
2020-11-04 17:02 ` BUG Randall S. Becker
2020-11-04 17:54 ` BUG Randall S. Becker
  -- strict thread matches above, loose matches on Subject: below --
2020-06-26 21:11 bug Luke Knoble
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Bug Santiago Torres
2016-09-14 22:14 ` Bug Dennis Kaarsemaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALG6MqwdCmwS5D_F9+q6UYzGm5ZzLL7Bi=rD7Ph2XE0uccu+xg@mail.gmail.com' \
    --to=alexmarginean16@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).