Git：如何将仅跟踪的文件推到远程

Question

I've seen many variants of this question on SO but none of them had what I looking for. Say I have a repo ~/MyRepo/ :

$ ls -a ~/MyRepo
code.r junk.txt .git

In MyRepo only the file code.r is being tracked, and junk.txt is not tracked. And say I have a remote (eg on Dropbox) at ~/Dropbox/MyShare/ that a friend has access to (only for reading). The intent is for this remote to only contain my latest committed version of code.r , and not contain junk.txt . I'm trying to achieve the following: whenever I commit code.r I want to be able to update (automatically if possible) the remote ~/Dropbox/MyShare/code.r with the committed version of ~/MyRepo/code.r .

I am aware of .gitignore but not interested in that route because I have several untracked files that I want to ignore, and I only want to "push" the files I'm tracking to the remote. I also tried the approach of doing a cloning into ~/Dropbox/MyShare/ but cloning or pulling always seem to include tracked and untracked files, thus polluting my Remote.

My current solution is to have a post-commit hook under ~/MyRepo/.git/hooks/ that has explicit commands to individually copy all the "files I care about" to the remote. I don't like this solution because the "files I care about" can change, and I don't have to go and update the post-commit hook.

I am hoping there is a way to automatically make the last-committed versions available in ~/Dropbox/MyShare/ by some combination of git commands. I don't mind doing a single manual "push" command every time I commit in ~/MyRepo/ .

Here is what I tried based on one of the answers below, but I am still stumped.

# create my repo
mkdir foo
cd foo
git init
touch fileA fileB fileC
git add fileA
git commit -m 'new'

# now create remote 
mkdir ../foo_remote
cd ../foo_remote
git init
cd ../foo
git remote add foo_remote ../foo_remote

bash-3.2$ git remote -v                                                                                                                                                                                                                                                         
foo_remote      ../foo_remote (fetch)                                                                                                                                                                                                                                           
foo_remote      ../foo_remote (push)                                                                                                                                                                                                                                            

Now when I try to push, I get this mean error message:

bash-3.2$ git push foo_remote master                                                                                                                                                                                                                                            

Counting objects: 3, done.                                                                                                                                                                                                                                                      
Writing objects: 100% (3/3), 207 bytes, done.                                                                                                                                                                                                                                   
Total 3 (delta 0), reused 0 (delta 0)                                                                                                                                                                                                                                           
Unpacking objects: 100% (3/3), done.                                                                                                                                                                                                                                            
remote: error: refusing to update checked out branch: refs/heads/master                                                                                                                                                                                                         
remote: error: By default, updating the current branch in a non-bare repository                                                                                                                                                                                                 
remote: error: is denied, because it will make the index and work tree inconsistent                                                                                                                                                                                             
remote: error: with what you pushed, and will require 'git reset --hard' to match                                                                                                                                                                                               
remote: error: the work tree to HEAD.                                                                                                                                                                                                                                           
remote: error:                                                                                                                                                                                                                                                                  
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to                                                                                                                                                                                                
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into                                                                                                                                                                                                
remote: error: its current branch; however, this is not recommended unless you                                                                                                                                                                                                  
remote: error: arranged to update its work tree to match what you pushed in some                                                                                                                                                                                                
remote: error: other way.                                                                                                                                                                                                                                                       
remote: error:                                                                                                                                                                                                                                                                  
remote: error: To squelch this message and still keep the default behaviour, set                                                                                                                                                                                                
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.                                                                                                                                                                                                  
To ../foo_remote                                                                                                                                                                                                                                                                
 ! [remote rejected] master -> master (branch is currently checked out)                                                                                                                                                                                                         
error: failed to push some refs to '../foo_remote'           

Any ideas where I'm going wrong?

Answer 1

If you do not add the file why would it be pushed to the remote - simple answer do not add files to you local repo you do not want pushed.

Either put the files in the repo or do not - the point of a DVCS is to have the same files everywhere.

I would look again at .gitignore it works - you can keep it locally and not include it in the repo if you do not want to share it - this is the sole purpose of this file and the fact you do not want to use it seems odd. Bit like saying I want to compile C files but I do not want to use a compiler

mkdir foo
cd foo
git init
touch fileA fileB fileC fileD
git add fileA
git commit -m "New file"
git push

Only fileA will get pushed

Answer 2

This doesn't directly answer your question but it's also a bit long for a comment and I wanted to share it anyway. It may help some from going through the pain I felt.

So my advice from experience is:

Don't mix Dropbox and github repositories.

I got burned a couple of times with this with conflicts for nearly every file getting generated.

I now always keep my github (ie rails) projects in a different folder.

I create ~/Dropnot as the name for this different folder.
As always I create an alias in my .bash_aliases file, in this case alias not='cd ~/Dropnot'

When I am setting up a new machine however, I often use a Dropbox/xfer folder to quickly do a 1 time setup to transfer all my Dropnot files (I copy them there on another machine just for that).
Going forward I then use fetch/pull/push for changes to the various repos under that directory.