Incorporating a fork's contributions into your own repo — permission required?

This question might be closed, but honestly, I have no idea where else to ask it. It seems silly, but I think could become quite serious if not handled correctly.

The scenario is this.

  • How to git-pull all but one folder
  • Is HEAD in git case insensitive on all platforms?
  • Preventing others from force-pushing to my Git repository
  • Git Windows Disable password prompt UI but get password prompt from shell
  • way to combine all commits into a single commit using libgit2
  • Git remembers submodule's remote and history even after removing it
  • Someone has forked your repository on Github. They have implemented a standard that you are really interested in and want to apply it to your own repository, although this person has left no contact information.

    Should you go ahead and add that person’s implementation to your own repository? (obviously giving the author credit on his implementation)

    Is there away to mention this person in your commit message?

    Or…

    Should you back off and not worry about it because that person’s forked repo is their own?

    I suppose there is no easy answer, I am just looking for someone who has perhaps had experience with this issue to give their best advice.

  • Teamcity: ssh socks5 authentication
  • gitignore my windows username
  • git rm - fatal: pathspec did not match any files
  • Bare repo: Not all refs have been pushed
  • Integrate multiples projects in one big project (Ionic 3)
  • How can I avoid ignored files when I checkout a subtree branch?
  • One Solution collect form web for “Incorporating a fork's contributions into your own repo — permission required?”

    There is, indeed, an easy answer. All projects on Github are recommended to have a license — for public repositories, that is usually an open source license (or otherwise having the source public doesn’t make much sense).

    While the details may vary, those licenses usually allow you to use (and possibly modify) the source while giving adequate credit.

    Git (and Github, especially with forks), makes this easy. You pull in the commit(s) from the fork into your own repo’s history. The committer information will be maintained, thus providing credit to who first introduced the code into the aggregate histories.

    So basically, unless their license restricts you from using their code without permission, you can include their changes into your own repo. Talking to them is always a good idea (remember that every Git commit must contain an email address, so you can easily find out their contact details), but for FOSS not always necessary.

    On Github, you can also use the Issues feature of a repo (if enabled) to contact them and ask about this.

    Git Baby is a git and github fan, let's start git clone.