On Thu, Sep 01, 2022 at 11:48:10AM -0700, Frederick Brier wrote: > This is odd configuration. A git repo is created on a file share, or in a > directory on a machine. From another directory, you clone the repo, using a > folder path. In the cloned repo its remote origin is the first repo, > showing the branches are identical. You make a change in the cloned repo, > commit, and try to push. git comes back with "remote: error: refusing to > update checked out branch: refs/heads/master" as if you are pushing into a > non-bare repo that is not in sync with the one you are pushing. Why? And > what needs to be done to make this work? Thank you.
Is the first repository - "created on a file share, or in a directory on a machine" - a bare one or not? And while we're at it, which protocol the file share is served using? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20220905103905.ra4oxyj7ofkhsxd7%40carbon.
