how to apply a git patch as if the author committed to my repo?

11,746

Solution 1

B could create and send a bundle rather than a patch. This allows sending commits when none of the transports available for push or fetch will work.

Solution 2

git am is what you're looking for. Ask him to commit locally and do git format-patch. This will create a patch. You can then use git am to add it to your repo.

Share:
11,746
a1an
Author by

a1an

Updated on June 05, 2022

Comments

  • a1an
    a1an about 2 years

    Lets suppose there is a central repository where commits from satellite ones are pushed some time. Developer A makes some commits on his repo while B makes some on his own too.

    Now, A wants to incorporate one of B's commits into his repo (which he cannot access directly to pull).

    One way is to have B create a patch and send it to A but in that case there are two problems: 1. The patch will appear as local modifications to A who have then to commit it (with its own name) 2. Once the central repo is updated the changes will conflict (being pushed by two different authors).

    Is there a way to have the patch applied directly "as a commit" on local A repo so that it will appear to him as if it were pulled from the central repo (i.e. origin)?

    PS: (this might not apply: see comments: is there a way to strike text until verified?) After some more investigation and testing looks like also git am < git-formatted-patch would make it so that the patch appears committed to the local master (then I hope it will be recognized as the same commit when B pushes it to the central repo). It looks like it is git apply that leaves the patch uncommitted...

  • Mutant Bob
    Mutant Bob almost 5 years
    What if the author is on vacation and all you have is the diff? Is there a way to commit the changes to the local repo as a specific identity?
  • qqx
    qqx almost 5 years
    The easiest way would be to use git apply to modify the files then git -c author.name="<author name>" -c author.email="<author email>" commit. But this is quite unrelated to the original question. This will not preserve the commit ID. In addition to the differences I noted in my comment on the question, the author time would also vary from any commit created by the author.