`git pull` is really just a shorthand for `git pull &lt;remote&gt; &lt;branchname&gt;`, in most cases it&#39;s equivalent to `git pull origin master`. You will need to add another remote and pull explicitly from it. This page describes it in detail:

http://help.github.com/forking/

`upstream` in the github example is just the name they&#39;ve chosen to refer to that repository.  You may choose any that you like when using `git remote add`.  Depending on what you select for this name, your `git pull` usage will change.  For example, if you use:

`git remote add upstream git://github.com/somename/original-project.git`

then you would use this to pull changes:

`git pull upstream master`

But, if you choose origin for the name of the remote repo, your commands would be:

To name the remote repo in your local config: `git remote add origin git://github.com/somename/original-project.git`

And to pull: `git pull origin master`

In jQuery, is it possible to &lt;em&gt;invoke a callback&lt;/em&gt; or &lt;em&gt;trigger an event&lt;/em&gt; after an invocation of `.each()` (or any other type of iterative callback) has &lt;strong&gt;completed&lt;/strong&gt;.

For example, I would like this &quot;fade and remove&quot; to complete

    $(parentSelect).nextAll().fadeOut(200, function() {
        $(this).remove();
    });

before doing some calculations and inserting &lt;em&gt;new&lt;/em&gt; elements after the `$(parentSelect)`. My calculations are incorrect if the existing elements are still visible to jQuery and sleeping/delaying some arbitrary amount of time (200 for each element) seems like a brittle solution at best.

I can easily `.bind()` the necessary logic to an event callback but I&#39;m not sure how to cleanly invoke the `.trigger()` after the above iteration has &lt;em&gt;completed&lt;/em&gt;. Obviously, I can&#39;t invoke the trigger inside the iteration as it would fire multiple times.

In the case of `$.each()`, I&#39;ve considered adding something to the end of the data argument (that I&#39;d manually look for in the iteration body) but I&#39;d hate to be forced to that so I was hoping there was some other elegant way to control the flow with respect to iterative callbacks.

Invoking a jQuery function after .each() has completed

I used a variable with a lot of data in it, say `String data`.
I wanted to use a small part of this string in the following way:
 
    this.smallpart = data.substring(12,18);

After some hours of debugging (with a memory visualizer) I found out that the objects field `smallpart` remembered all the data from `data`, although it only contained the substring.

When I changed the code into:

    this.smallpart = data.substring(12,18)+&quot;&quot;; 

..the problem was solved! Now my application uses very little memory now! 

How is that possible? Can anyone explain this? I think this.smallpart kept referencing towards data, but why? 

**UPDATE:**
How can I clear the big String then? Will data = new String(data.substring(0,100)) do the thing?

Why does appending &quot;&quot; to a String save memory?

I have created a fork from a project on GitHub.
How can I now pull changes from the project that I forked from?

Git: Pull from other remote

<p>I have created a fork from a project on GitHub.
How can I now pull changes from the project that I forked from?</p>


`ref^` refers to the commit before `ref`. What about getting the commit *after* `ref`?

For example, if I `git checkout 12345`, how do I check out the next commit?

PS: Yes, Git&#39;s a [DAG][1] node pointer struct tree whatever.  **How do I find the commit after this one?**

  [1]: https://en.wikipedia.org/wiki/Directed_acyclic_graph



How do I find the next commit in Git? (child/children of ref)

For deploying to Heroku, I use `git push heroku master`. But how do I see which revision I pushed up to heroku? (I&#39;m often in doubt if I pushed the recent version up)

For those not familiar with it, Heroku&#39;s create script generates a remote git repository that you push to. Upon push, the code is deployed magically.

Heroku adds a remote repository to the local one in the form:

    $ git remote add heroku git@heroku.com:appname.git
More info in Heroku&#39;s manual [&quot;Deploying with Git&quot;][1]

Question is: How can I see latest version in Heroku repository?

  [1]: http://docs.heroku.com/git

How to view remote Git revision on Heroku

Tim Pope argues for a particular Git commit message style in his blog post:
&lt;http://www.tpope.net/node/106&gt;.

Here is a quick summary of what he recommends:

* First line is 50 characters or less.
* Then a blank line.
* Remaining text should be wrapped at 72 characters.

His blog post gives the rationale for these recommendations (which I will call “50/72 formatting” for brevity):

* In practice, some tools treat the first line as a subject line and the second paragraph as a body (similar to email).
* `git log` does not handle wrapping, so it is hard to read if lines are too long.
* `git format-patch --stdout` converts commits to email — so to play nice it helps if your commits are already wrapped nicely.

A point I would like to add that I think Tim would agree with:

* The act of summarizing your commit is a good practice inherently in any version control system. It helps others (or a later you) find relevant commits more quickly.

So, I have a couple of angles to my question:

* What chunk (roughly) of the “thought leaders” or “experienced users” of Git embrace the 50/72 formatting style? I ask this because sometime newer users don’t know or don’t care about community practices.
* For those that don’t use this formatting, is there a principled reason for using a different formatting style? (Please note that I’m looking for an argument on the merits, not “I’ve never heard of it” or “I don’t care.”)
* Empirically speaking, what percentage of Git repositories embrace this style? (In case someone wants to do an analysis on GitHub repositories… hint, hint.)

My point here is not to recommend the 50/72 style or shoot down other styles. (To be open about it, I do prefer it, but I am open to other ideas.) I just want to get the rationale for why people like or oppose various Git commit message styles. (Feel free to bring up points that haven’t been mentioned, too.)

Git Commit Messages: 50/72 Formatting

I&#39;ve written a Git post-commit hook and it works correctly.  However, I want to add this hook to apply to all current (and future) Git repositories I am working on.  I tried adding the hook to my `~/.git/hooks/` directory instead of in the hooks directory in the project directory, however, this did not seem to work.

Is there a way to create global Git hooks that will apply to all repositories on my system (without having to copy them into each project directory)?  If not, what would be the best solution going forward -- perhaps a git-init template?





Applying a git post-commit hook to all current and future repositories

I have a project hosted on GitHub. I created a branch on one computer, then pushed my changes to GitHub with: 

    git push origin branch-name

Now I am on a different computer, and I want to download that branch. So I tried:

    git pull origin branch-name

...but all this did was overwrite my master branch with the changes in my new branch.

What do I need to do to properly pull my remote branch, without overwriting existing branches?

How to download a branch with git?

I&#39;ve got a little Bash script that I use to access twitter and pop up a Growl notification in certain situations. What&#39;s the best way to handle storing my password with the script? 

I would like to commit this script to the git repo and make it available on GitHub, but I&#39;m wondering what the best way to keep my login/password private while doing this is. Currently, the password is stored in the script itself. I can&#39;t remove it right before I push because all the old commits will contain the password. Developing without a password isn&#39;t an option. I imagine that I should be storing the password in an external config file, but I thought I&#39;d check to see if there was an established way to handle this before I tried and put something together.

What is the best practice for dealing with passwords in git repositories?

I created a new local Git repository:

    ~$ mkdir projectname
    ~$ cd projectname
    ~$ git init
    ~$ touch file1
    ~$ git add file1
    ~$ git commit -m &#39;first commit&#39;

**Is there any git command to create a new *remote* repo and push my commit to GitHub from here?** I know it&#39;s no big deal to just fire up a browser and head over to [Create a New Repository][1], but if there is a way to achieve this from the CLI I would be happy.

I read a vast amount of articles but none that I found mention how to create a remote repo from the CLI using git commands. Tim Lucas&#39;s nice article [Setting up a new remote git repository][2] is the closest I found, *but GitHub does not provide shell access*.

  [1]: https://github.com/new
  [2]: http://toolmantim.com/thoughts/setting_up_a_new_remote_git_repository

Is it possible to create a remote repo on GitHub from the CLI without opening browser?

I have a private repository on Github for a project I&#39;m working on.  Until now I had only worked on my home desktop, but I just bought a laptop, and am trying to set it up so that I can work on the project from either computer, and push / pull changes.  

I added a new SSH key to my Github account for the laptop, and was successful in cloning and making changes to a public test repo that I set up.  However, I couldn&#39;t clone the private repo.  Is there anything special I need to do in the command line in order to clone a private repo?  Do I need to set up a new GitHub account for my laptop and set myself up as a collaborator?

The command I used was `git clone git://github.com/username/reponame.git`

Clone A Private Repository (Github)

I intend to share my source code on an invite-only basis to a few dozen users maybe. The source code itself should not be public. Participants are allowed and encouraged to submit their changes. So I need source control, preferably Git, hosted on a public server with private access for multiple users.

I learned that it is possible to set up private Git repositories on GitHub which use https:// links. On GitHub itself such a project does not show up in searches. For participating users the project shows a &quot;lock&quot; icon. So there are obviously private repositories; I just don&#39;t know how set one up. A lot of tutorials use SSH to set up private repositories but they all require you to have &quot;your own server&quot;.

I don&#39;t care about secure connections when pushing/pulling source code nor do I have trust issues with GitHub. All I care about is giving access only to users I invite. Maybe I&#39;m naive and such a solution is only available via commercial hosting (e.g., [Unfuddle][1], [Assembla][2]), but if not, I&#39;d really like to know how it&#39;s done!

  [1]: https://unfuddle.com/
  [2]: https://en.wikipedia.org/wiki/Assembla




How do I set up a private Git repository on GitHub? Is it even possible?

I am having a strange issue that I can&#39;t seem to resolve. Here is what happend:

I had some log files in a github repository that I didn&#39;t want there. I found this script that removes files completely from git history like so:

        #!/bin/bash
    set -o errexit
     
    # Author: David Underhill
    # Script to permanently delete files/folders from your git repository.  To use 
    # it, cd to your repository&#39;s root and then run the script with a list of paths
    # you want to delete, e.g., git-delete-history path1 path2
     
    if [ $# -eq 0 ]; then
        exit 0are still
    fi
     
    # make sure we&#39;re at the root of git repo
    if [ ! -d .git ]; then
        echo &quot;Error: must run this script from the root of a git repository&quot;
        exit 1
    fi
     
    # remove all paths passed as arguments from the history of the repo
    files=$@
    git filter-branch --index-filter &quot;git rm -rf --cached --ignore-unmatch $files&quot; HEAD
     
    # remove the temporary history git-filter-branch otherwise leaves behind for a long time
    rm -rf .git/refs/original/ &amp;&amp; git reflog expire --all &amp;&amp;  git gc --aggressive --prune


I, of course, made a backup first and then tried it. It seemed to work fine. I then did a git push -f and was greeted with the following messages:

    error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
    error: Cannot update the ref &#39;refs/remotes/origin/master&#39;.

Everything seems to have pushed fine though, because the files seem to be gone from the GitHub repository, if I try and push again I get the same thing:

    error: Unable to append to .git/logs/refs/remotes/origin/master: Permission denied
    error: Cannot update the ref &#39;refs/remotes/origin/master&#39;.
    Everything up-to-date

**EDIT**

    $ sudo chgrp {user} .git/logs/refs/remotes/origin/master
    $ sudo chown {user} .git/logs/refs/remotes/origin/master
    $ git push
    Everything up-to-date

Thanks!

**EDIT**

Uh Oh. Problem. I&#39;ve been working on this project all night and just went to commit my changes:

    error: Unable to append to .git/logs/refs/heads/master: Permission denied
    fatal: cannot update HEAD ref

So I:

    sudo chown {user} .git/logs/refs/heads/master
    sudo chgrp {user} .git/logs/refs/heads/master

I try the commit again and I get:

    error: Unable to append to .git/logs/HEAD: Permission denied
    fatal: cannot update HEAD ref

So I:

    sudo chown {user} .git/logs/HEAD
    sudo chgrp {user} .git/logs/HEAD

And then I try the commit again:

    16 files changed, 499 insertions(+), 284 deletions(-)
    create mode 100644 logs/DBerrors.xsl
    delete mode 100644 logs/emptyPHPerrors.php
    create mode 100644 logs/trimXMLerrors.php
    rewrite public/codeCore/Classes/php/DatabaseConnection.php (77%)
    create mode 100644 public/codeSite/php/init.php
    $ git push
    Counting objects: 49, done.
    Delta compression using up to 2 threads.
    Compressing objects: 100% (27/27), done.
    Writing objects: 100% (27/27), 7.72 KiB, done.
    Total 27 (delta 15), reused 0 (delta 0)
    To git@github.com:IAmCorbin/MooKit.git
    59da24e..68b6397  master -&gt; master

Hooray. I jump on http://GitHub.com and check out the repository, and my latest commit is no where to be found. ::scratch head:: So I push again:

    Everything up-to-date

Umm...it doesn&#39;t look like it. I&#39;ve never had this issue before, could this be a problem with github? or did I mess something up with my git project?

**EDIT**

Nevermind, I did a simple:

    git push origin master

and it pushed fine.

Content Type	Original Author	Original Content on Stackoverflow
Question	Ran	View Question on Stackoverflow
Solution 1 - Git	Igor Zevaka	View Answer on Stackoverflow
Solution 2 - Git	user272390	View Answer on Stackoverflow

Git: Pull from other remote

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Why does appending "" to a String save memory?

Invoking a jQuery function after .each() has completed

Attributions