提交后Git不影响更改

Question

This is my first time trying to work with version control. As I found one of the best solution is Git.

I did almost everything correct and at least i got some problem or something like that.

Debian Machine.

/home/user/myProject/

git init --bare myproject.git

/var/www/clonedProject/

git clone /home/user/myProject/myproject.git
git add xxx.php
git commit -m "TEST"
git push origin master

but there is no changes in home/user/myProject. I don't understand what is problem about, if there is problem or what i am doing wrong.

Git documentation

Thanks.

Answer 1

Here's a complete test run using your example (as close as reasonably possible, anyway). You can see from this log that your commands should be working fine. If you get some different output, please share it with us so we can help you solve your real problem. Step by step:

1. create some directories to work with for this example

    $ mkdir bare $ mkdir clone 

2. initialize a bare repo called myproject.git

    $ cd bare/ $ git init --bare myproject.git Initialized empty Git repository in /example/bare/myproject.git/ 

3. change to the clone directory and clone the repo we just created

    $ cd ../clone $ git clone ../bare/myproject.git Cloning into 'myproject'... warning: You appear to have cloned an empty repository. done. 

4. change directory into the new repo, then create, add, and commit a new file

    $ cd myproject/ $ touch xxx.php $ git add xxx.php $ git commit -m "TEST" [master (root-commit) 921786a] TEST 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 xxx.php 

5. push this new commit back to origin (the bare repo we cloned from earlier)

    $ git push origin master # push this new commit to origin Counting objects: 3, done. Writing objects: 100% (3/3), 207 bytes, done. Total 3 (delta 0), reused 0 (delta 0) To /example/clone/../bare/myproject.git * [new branch] master -> master 

6. go back to the bare repo and see if the commit is there

    $ cd ../../bare/myproject.git/ $ git log commit 921786a20f3e7e0d17eec65450472b54bf3d7c56 Author: Carl Norum <carl@someplaceorother.com> Date: Wed Jul 3 08:00:31 2013 -0700 TEST 

7. It is, so everything worked fine.

Answer 2

your changes have been copied into the database in /home/user/myProject/myproject.git . they will not be automatically distributed to all other clones.

to see them in home/usr/myProject you have to make this folder a clone of the repository as well and issue a git pull . it's not a good idea to have the "bare" repository within the project itself.

instead you should probably use a separate git repository for all your "bare" repos. you then push changes from a clone "repositoryA" to a central "bare" repository, and pull the changes from that central repository into another clone "repositoryB"

$ cd ~
$ mkdir git
$ git init --bare git/myproject.git
$ cd git clone git/myproject myProject
$ ls
git/
myProject/
$ cd myProject/
$ ls
$ cd /var/www/clonedProject/
$ git clone /home/user/git/myproject.git
$ ls
myproject
$ cd myproject
$ touch xxx.php
$ ls
xxx.php
$ git add xxx.php
$ git commit -m "TEST"
$ git push origin master
$ cd ~/myProject
$ ls
$ git pull
$ ls
xxx.php
$

git itself is a "distributed" version control system, which means that the notion of a central repository is, well, inadequate. it means, that there is not a single server, but can be any number of "remote" servers, including none. however, if you have multiple clones of a single repository, it is usually advisable to have at least one shared "remote", that is only accessed via git pull and git push . in theory you can clone a non-bare repository (that is: a working directory under git control) directly, but it is usually troublesome to push back to such a repository - mainly because you create a hierarchy of access rights.

Answer 3

This might be a very good tutorial to get you started. Tutorial

Try git commit -a -m "TEST"

Answer 4

Have you made a connection between your lokal repo and the remote repo?

Try: git remote add origin /home/user/myProject/