Does not appear to be a git repository как исправить

I am following the instructions given here to create a Git repository. All went well until the last line:

$ git push -u origin master  

fatal: ‘origin’ does not appear to be a git repository
fatal: The remote end hung up unexpectedly

I’m using git version 1.7.11.3 on OS X 10.6.8

$ git remote -v  

returns nothing

Config file for the repository:

[core]
repositoryformatversion = 0  
filemode = true  
bare = false
logallrefupdates = true  
ignorecase = true  

I’ve had to open sudoers file using sudo visudo command and add the following to it (under # User privilege specification):

git ALL=(ALL) ALL.  

Now if I do:

$ git remote add origin /Volumes/500GB/git-repository/myproject.git  

it comes back with no error, but I don’t see any code in the repository
(it has the aforementioned directories like branches, hooks, …)

If I do:

$ git push -u origin master  
fatal: 'origin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

$ git remote -v   
origin /Volumes/500GB/git-repository/myproject.git (fetch)     
origin /Volumes/500GB/git-repository/myproject.git (push)

Fatal error: does not appear to be a Git repository. This frustrating error is no stranger to Git users. And it can be difficult to track down a root cause if you don’t know where to start looking. But before you give up on Git, you can easily learn what causes this error, how to diagnose it, and how to avoid it in the future.

• Learn what causes the error
• Make sure your repository is recognized as a Git project
• Check the file path

What Causes The “Does Not Appear To Be a Git Repository” Error?

The “… does not a appear to be a git repository” error is triggered when you try to clone, or run other commands, in a directory that is not recognized as a Git repository. The directory or remote file path might not have initialized Git, or the file path you are trying to access as an active repository is incorrect.

At the most basic level, Git is basically indicating that the repository you are trying to work with is unrecognizable as a Git project. This is why the error can be frustrating if you believe you have set everything up correctly. But have no fear, a simple typo may have triggered the error. Read on to learn what you can check in order to diagnose and treat this error.

What Is a Git Repository Anyway?

When working with Git repositories you are working, in essence, with directories that have been initialized as Git projects. Virtually any directory in your local computer, or on a remote server, can be initialized with Git.

In order to properly diagnose why your Git project is not accepting commands or why your remote repositories are not being recognized you must understand what Git is looking for when it is trying to interact with a repository.

New to Git? Check out the full Git guide for beginners.

Any directory, local or remote, must be initialized with Git. As you might recall, this means you must run the Git initialization command:

git init

If you have run this command in a local directory then that directory becomes a Git repository. You will see a success message indicating that the command was successful. You will also notice that all Git repositories have a .git directory where critical files and reference points are saved.

If you are initializing a remote repository, it is customary to use the --bare option:

git init --bare

This sets up a “bare” repository, which in essence is a blank directory, initialized with Git, and able to receive and run Git commands that are sent to it. Bare repositories are an ideal “hub” from which one or many Git users can clone a project, push, and pull.

Checking the File Path Of Your Remote Repository

A Git user will often encounter will encounter the “… does not appear to be a Git repository” error when trying to clone, push, or pull content from a remote repository. Be sure to check the file path of the remote repository. There are a few different ways to do that.

If you are cloning, double check to make sure that you have necessary access to the repository. Unless you are cloning a public repository on GitHub, you are likely using SSH to make the connection. Check out our full guide on setting up your remote repository with Git.

Likewise, you will want to check out the syntax of your clone command. For example, here is a basic clone command that uses HTTP to make the connection to the repository:

git clone https://github.com/WordPress/WordPress.git

If you run this command in your favorite terminal emulator it will create a directory called “WordPress” with all of the WordPress core files intact. It will also contain the .git directory, and all of the history of the project. This directory will therefore be a fully functional, local git repository. It will also have the remote repository (at GitHub) information properly set up.

But if you are reaching out to a private server that does not have HTTP access available you have to change this syntax to include a server user with appropriate privilege. (This is why when setting up a private Git server it is a good idea to create a special “Git” user with access to the repository.)

git clone [email protected]:/home/user/production.git

Notice that unlike the HTTP variation from GitHub, this clone URL contains [email protected]. The “user,” in this case, is a server user with access and privileges to interact with the Git repository on the server. The destination is the hostname, domain name, or IP address of the server you are trying to contact. Then, a colon (:) separates the user and server declaration from the file path.

The file path is critical here. The file path indicates the exact location and name of your repository. In the example above, the repository is a directory called production.git.

Always make sure to use a .git extension on your repository directory.

The production.git directory resides in the user’s home directory: /home/user.

You must reproduce this syntax precisely, otherwise you will receive the “Does not appear to be a Git repository” error.

Well done! You now know how to treat the “Does not appear to be a Git repository” error.

Let our Managed Hosting team configure your servers while you work on building your brand!

Back to top button

fatal: 'origin' does not appear to be a git repository

fatal: The remote end hung up unexpectedly

[core]

    repositoryformatversion = 0

    filemode = true

    bare = false

    logallrefupdates = true

[branch "master"]

[branch "MOODLE_23_STABLE"]

[branch "MOODLE_24_STABLE"]

[remote "upstream"]

    url = git://git.moodle.org/moodle.git

    fetch = +refs/heads/*:refs/remotes/upstream/*

5 ответов:

This article outlines the steps necessary to solve the fatal: 'origin' does not appear to be a git repository error in Git. This error is associated with the git push origin <branch-name> command.

Here are some of the most probable causes of the fatal: 'origin' does not appear to be a git repository error.

1. Your remote fork (origin) might be missing.
2. Your remote’s URL configuration might have changed.

If you initialize a local repo with the git init command and fail to link the repo with a remote repository, you will get the same error if you attempt to push the changes.

Fix the fatal: 'origin' does not appear to be a git repository Error in Git

We now know why this error pops up on Git. How do we fix it?

We first need to check if our local repository has an origin. We will run the command below.

If you can’t see the origin listed in the output, your origin remote repo might be missing, or you did not link your local repo with a remote repository.

To set it up, go to your GitHub account where the remote repository is located and follow the steps below.

1. On your GitHub account, go to Repositories and select the repository you want to link your local repo.

   

2. Click on Code and copy the link to your repository.

   

3. On the Git terminal, run the command below to add origin to your repo.

   $ git remote add origin<URL>
   

   In our case:

   $ git remote add origin https://github.com/Wachira11ke/Git-Tutorials.git
   

As shown below, we can run the git branch command to check for remote branches in our repo.

Output:

* master
  remotes/origin/master

As shown below, we can now push our code by running the git push origin master command.

The command above will push to our origin and create a branch called master.

If the issue persists, your URL might not be referenced correctly. We can run the command shown below to rectify this issue.

$ git remote set-url origin ssh://git@github.com/gitusername/newRepositoryName.git

You can also change your master to origin if the above methods do not help. Just run:

In conclusion, we have covered three methods you can use to solve the error mentioned above on Git. Always link a local repo with a remote repo before pushing code.