4 ms·

FWIW, for smaller drive-by fixes you may press the Edit button directly on a file in some else’s repo.

• bastawhiz 9y ago
  And in truth, the "github crap" is clicking "Fork" and running "git remote add". Pushing and filing a PR are the same process.
  • lozenge 9y ago
    Except your fork now prominently appears even after the PR is merged. However, I don't think Github has a way to see all your PRs.
    • shlomi-noach 9y ago
      Here's how to see all your PRs: https://github.com/search?q=is:pr+author:YOURNAME&type=Issues&ref=searchresults https://github.com/search?q=is:pr+author:YOURNAME&type=Issue... Here's how to see all your open PRs: https://github.com/search?q=is:pr+is:open+author:YOURNAME&type=Issues&ref=searchresults https://github.com/search?q=is:pr+is:open+author:YOURNAME&ty... Replace YOURNAME with your GitHub handle, or pick your colleagues names.
      • zie 9y ago
        Nice, thanks!
  • zie 9y ago
    Right, nothing you can do from a git client, unlike a patch.
    • bastawhiz 9y ago
      It's a website. If you want to do it entirely from your terminal, you can use their API. Patches require you to share the patch somewhere. Your just sharing the patch to a different interface.
      • zie 9y ago
        Sure, but the GitHub API doesn't accept patches either, near as I can tell. You MUST create a pull request, which requires a fork: https://developer.github.com/v3/pulls/#create-a-pull-request https://developer.github.com/v3/pulls/#create-a-pull-request Unless you know something I don't?
• zie 9y ago
  Yes, but the built in web editor is not very nice. So you have to copy/paste it, and of course you want to test and make sure it works first, etc, etc. I think allowing patches is just a better solution here.