No. Hooks are per-repository and are never pushed. Similarly, the repo config isn&#39;t pushed either, nor is anything in `.git/info`, or a number of other things.

Pushing and pulling only exchanges branches/tags and commit objects (and anything reachable from a commit, e.g. trees, blobs).

No, git hooks are not pushed or pulled, as they are not part of the repository code.

Please refer to [the documentation][1] for a list of simple client-side and server-side hooks.

If you want to enable some hooks for all clients that clone or pull from a given repository, you have to add the hooks to your codebase and then create your own script to copy them into, or link to them from `repo/.git/hooks/`.

  [1]: http://git-scm.com/book/en/Customizing-Git-Git-Hooks

Sadly no but since git 2.9 you can place them into .githooks folder (as others mentioned) and run:

    git config --local core.hooksPath .githooks/

So no need of symlinks or copy files.

I&#39;m taking some JavaScript/jQuery lessons at codecademy.com. Normally the lessons provide answers or hints, but for this one it doesn&#39;t give any help and I&#39;m a little confused by the instructions. 

It says to make the function makeGamePlayer return an object with three keys. 



    //First, the object creator
    function makeGamePlayer(name,totalScore,gamesPlayed) {
        //should return an object with three keys:
        // name
        // totalScore
        // gamesPlayed
    }
    
   

I&#39;m not sure if i should be doing this

    //First, the object creator
    function makeGamePlayer(name,totalScore,gamesPlayed) {
        //should return an object with three keys:
        // name
        // totalScore
        // gamesPlayed

             this.name =  name;
             this.totalScore = totalScore;
             this.gamesPlayed = gamesPlayed;
    }


or something like this

     //First, the object creator
        function makeGamePlayer(name,totalScore,gamesPlayed) {
            //should return an object with three keys:
            // name
            // totalScore
            // gamesPlayed
    
             var obj = {
                 this.name =  name;
                 this.totalScore = totalScore;
                 this.gamesPlayed = gamesPlayed;
              }
        }
        
    
I have to be able to modify the properties of the object after its created. 

JavaScript: function returning an object

I would like some information on how to correctly think about C++11 closures and `std::function` in terms of how they are implemented and how memory is handled.

Although I don&#39;t believe in premature optimisation, I do have a habit of carefully considering the performance impact of my choices while writing new code.  I also do a fair amount of real-time programming, e.g. on microcontrollers and for audio systems, where non-deterministic memory allocation/deallocation pauses are to be avoided.

Therefore I&#39;d like to develop a better understanding of when to use or not use C++ lambdas.

My current understanding is that a lambda with no captured closure is exactly like a C callback.  However, when the environment is captured either by value or by reference, an anonymous object is created on the stack.  When a value-closure must be returned from a function, one wraps it in `std::function`.  What happens to the closure memory in this case?  Is it copied from the stack to the heap?  Is it freed whenever the `std::function` is freed, i.e., is it reference-counted like a `std::shared_ptr`?

I imagine that in a real-time system I could set up a chain of lambda functions, passing B as a continuation argument to A, so that a processing pipeline `A-&gt;B` is created.  In this case, the A and B closures would be allocated once.  Although I&#39;m not sure whether these would be allocated on the stack or the heap.  However in general this seems safe to use in a real-time system.  On the other hand if B constructs some lambda function C, which it returns, then the memory for C would be allocated and deallocated repeatedly, which would not be acceptable for real-time usage.

In pseudo-code, a DSP loop, which I think is going to be real-time safe.  I want to perform processing block A and then B, where A calls its argument.  Both these functions return `std::function` objects, so `f` will be a `std::function` object, where its environment is stored on the heap:

    auto f = A(B);  // A returns a function which calls B
                    // Memory for the function returned by A is on the heap?
                    // Note that A and B may maintain a state
                    // via mutable value-closure!
    for (t=0; t&lt;1000; t++) {
        y = f(t)
    }

And one which I think might be bad to use in real-time code:

    for (t=0; t&lt;1000; t++) {
        y = A(B)(t);
    }

And one where I think stack memory is likely used for the closure:

    freq = 220;
    A = 2;
    for (t=0; t&lt;1000; t++) {
        y = [=](int t){ return sin(t*freq)*A; }
    }

In the latter case the closure is constructed at each iteration of the loop, but unlike the previous example it is cheap because it is just like a function call, no heap allocations are made.  Moreover, I wonder if a compiler could &quot;lift&quot; the closure and make inlining optimisations.

Is this correct?  Thank you.

C++11 lambda implementation and memory model

If I create a new hook script in my local repository in repo/.git/hooks/post-commit and then I run &quot;git push&quot; are the hooks pushed to the remote?  Then, when the other developers run &quot;git pull&quot; from the same origin will they get my new hooks? 

Are git hooks pushed to the remote when I &#39;git push&#39;?

<p>If I create a new hook script in my local repository in repo/.git/hooks/post-commit and then I run "git push" are the hooks pushed to the remote?  Then, when the other developers run "git pull" from the same origin will they get my new hooks?</p>


I&#39;ve looked at all of the other ambiguous refname questions and none of them seem to help. Why am I getting this warning?
    
    $ git checkout master
    warning: refname &#39;master&#39; is ambiguous.
    $ git show-ref master
    eef61c00da690f093063ac5a728e22fd21648104 refs/heads/master
    $ git branch -a
      checkers
      exercises
    * master
    $ git remote -v
    $ 

Refname &#39;master&#39; is ambiguous

Both `git am` and `git apply` can be used to apply patches. I fail to see the difference. I see a difference now: `git am` automatically commits whereas `git apply` only touches the files but doesn&#39;t create a commit. Is that the only difference?

What is the difference between git am and git apply?

I&#39;d like to show all configured Git sections.

I only found `git config --get core.editor`, and I&#39;d like to output everything that&#39;s configured globally, not only the configured default editor.


How do I show my global Git configuration?

I have an Amazon EC2 machine. I would like to clone an older version of github repo on this machine. Normally I use git clone https://linktomyrepo.git How can I clone an older version, say an update from 14 days ago? I can see the exact version I need in the commit history of repository, but do not know how to clone it onto the EC2 machine. Do I need to use the little SHA code next to each commit?

Cloning an older version of github repo

I have a Git repository. I have cloned the repository and can commit my local changes. When I push my changes to the server it works.

As soon as I create a branch, I checkout the branch, commit my work and then checkout the master branch. I then merge my local changes into the master branch. When I try to push to the server I get the following exception:

    Welcome to Git (version 1.7.11-preview20120620)

    Run &#39;git help git&#39; to display the help index.
    Run &#39;git help &lt;command&gt;&#39; to display help for specific commands.

    $ git push origin master:master
     Counting objects: 9, done.
     Delta compression using up to 4 threads.
     Compressing objects: 100% (7/7), done.
     Writing objects: 100% (8/8), 13.68 KiB, done.
     Total 8 (delta 2), reused 1 (delta 0)
     Unpacking objects: 100% (8/8), 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 &#39;git reset --hard&#39; to match
     remote: error: the work tree to HEAD.
     remote: error:
     remote: error: You can set &#39;receive.denyCurrentBranch&#39; configuration variable to

     remote: error: &#39;ignore&#39; or &#39;warn&#39; 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: &#39;receive.denyCurrentBranch&#39; configuration variable to &#39;refuse&#39;.
     To c:/jGit
     ! [remote rejected] master -&gt; master (branch is currently checked out)
     error: failed to push some refs to &#39;c:/gitRepository&#39;

One solution is to run the following command:

    git config receive.denyCurrentBranch ignore

**After this it works, but I would like to know why I need to use this option. Is this the only option? What are the consequences of doing this?**

What I would really like to do is create branches, merge them into the master branch and then push my changes to the server.

What are the consequences of using receive.denyCurrentBranch in Git?

Before I do a small release and tag it, I&#39;d like to update the package.json to reflect the new version of the program.

Is there a way to edit the file ``package.json`` automatically?

Would using a ``git pre-release hook`` help?

update package.json version automatically

We are a team of 60+ developers working on the same product and are moving from SVN to Git and GitHub. We have a process in SVN where in individual files are locked and whenever a developer wants to commit code, he needs to get it unlocked by the owner of the file. Three of us are the owners of the total 150+ files. The unlocking is preceded by a code review. 

In Github, we are planning to use the Fork-Clone model - each project a group of dev is working on will do a fork, each developer will do a clone of the fork, write the code &amp; commit to origin, the lead of the feature will do a pull request to upstream.

Though this seems fine, the problem is when a big project gets delivered, it brings in lots of changes for review and hence, increases the load for the file owners. Also, this might happen in the later cycles of development and hence the project might be jeopardized.

One method we thought might work is to have hooks when the git push is done to the origin (fork). There can be one final review git pull to upstream. 

However, we could not find any github extensions or push hooks for the same. Is there a quick way (read, existing extension) to do this with Github or should we use the same hooks that we would use with git?

Is there a way to lock individual files or directories on fork when using git?

The question says it all. Is there a way to perform an action before a merge? I&#39;m guessing there&#39;s a way to make use of a `pre-commit` hook, but I&#39;m not quite sure.

How would I write a pre-merge hook in Git?

I have run gitlabhq rails server on virtual machine, following 1-6 steps from this tutorial https://github.com/gitlabhq/gitlab-recipes/blob/master/install/centos/README.md and starts rails server executing command `sudo -u git -H bundle exec rails s -e production`. After that I created user, using admin tools and created new project under this user. Then I&#39;m trying to push the existing project to this repo as always. But in the last step, `git push origin master` fails with the error 

&gt; [remote rejected] master -&gt; master (pre-receive hook declined)

Additional info:

1) I haven&#39;t activated user (project owner) via email activation link, because I haven&#39;t configured post service on server-side and I didn&#39;t find instructions how to do that in this manual.

2) Gitlab server generates tips how to push project to repo and there is not `repositories/` in path. I mean it generates `git@mygitlabhost:user/repo.git` instead of `git@mygitlabhost:repositories/user/repo.git` which is correct.

3) When i tried to debug it, I opened `pre-receive` script inside repo on server and tried to output variables (there is 3 of them): `refs = ARGF.read`, `key_id  = ENV[&#39;GL_ID&#39;]` and `repo_path = Dir.pwd` and found, that key_id is always empty. Maybe the problem is here... If so, please give me suggestions on how to fix that. Thanks

Git push error pre-receive hook declined

I am making changes to a project in a branch that, so far, is known to no one else but me.  However, starting recently, when I `git push` to this project, I now receive this as part of the response:

    remote: Create pull request for &lt;&lt;my branch&gt;&gt;:
    remote:   https://bitbucket.org/...

I have no idea why Git is giving me this message, which I have never seen before.

Even if I *delete* the remote branch (with &quot;`git push origin :&lt;&lt;my branch&gt;&gt;`&quot; I now *still* get this message! (I successfully **deleted** the branch on the remote, but the message remains)

Content Type	Original Author	Original Content on Stackoverflow
Question	slacy	View Question on Stackoverflow
Solution 1 - Git	Lily Ballard	View Answer on Stackoverflow
Solution 2 - Git	Marco Leogrande	View Answer on Stackoverflow
Solution 3 - Git	Marco Medrano	View Answer on Stackoverflow

Are git hooks pushed to the remote when I 'git push'?

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

C++11 lambda implementation and memory model

JavaScript: function returning an object

Attributions