Etiquette of GitHub Contributing, Pull Requests vs New Issue

I was wondering what the proper etiquette to contributing on GitHub is?

Should you submit a “New Issue” first and discuss the problem?

  • Why does global .gitignore file not appear to work_?
  • Retrieve private repository commits from github
  • git commit -m vs. git commit -am
  • delete first git commit
  • Git: Cloning through symlink requires password?
  • Github for windows changing line endings on commit
  • Or do you take some initiative, code, then do a “Pull Request” and discuss the code further there?

    My concern with creating a “New Issue” first is that if you do a “Pull Request” after, there would be two issues #’s created… seems like a waste.


  • Is it possible to wrap long lines in the GitHub diff viewer?
  • Removing Branches from GitHub
  • Post Commit Hook Not Running
  • Git Release with a Reverted Commit on master
  • Using RStudio to Make Pull Requests in Git
  • git behind proxy: remote HEAD refers to nonexistent ref, unable to checkout
  • One Solution collect form web for “Etiquette of GitHub Contributing, Pull Requests vs New Issue”

    The difference is quite clear:

    • if you don’t think you can contribute back a patch, open a “New Issue” (following the same kind of checklist than the one described here).
    • if you think you can make some patch to fix the issue, fork the repo, and make a “Pull Request” (once you have pushed your patch back to your fork).

    If you make a pull issue first, and then create a pull request, nothing stops you to reference the issue URL in your pull request comment, in order to avoid writing again the context of your patch.

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