cli/api
Mislav Marohnić d75faab85a Creating a PR now always prioritizes an existing fork as a push target
Before: the default push target for the current branch in `pr create`
was the first repository found among git remotes that has write access.

Now: the default push target is the fork the base repo, if said fork
exists and has write access, falling back to old behavior otherwise.

This change in the default is to facilitate contributions to projects
that have a hard requirement that all pull requests (even those opened
by people with write access to that project) come from forks.
2020-03-19 16:04:23 +01:00
..
client.go Tweak verbose HTTP logging 2020-02-21 12:57:00 +01:00
client_test.go Fix tests 2020-01-21 22:56:15 +01:00
fake_http.go sequental > sequential 2020-03-07 20:44:39 +00:00
pull_request_test.go Avoid crash when parsing in-progress CheckRuns 2019-11-19 09:42:59 +01:00
queries_issue.go Merge remote-tracking branch 'origin/master' into pr-count 2020-03-14 19:02:51 +05:00
queries_issue_test.go Add filter issues by author 2020-03-09 18:50:23 -06:00
queries_org.go Add ability to repo create within an org 2020-03-03 21:49:47 +01:00
queries_pr.go Merge remote-tracking branch 'origin/master' into pr-count 2020-03-14 19:02:51 +05:00
queries_repo.go Creating a PR now always prioritizes an existing fork as a push target 2020-03-19 16:04:23 +01:00
queries_repo_test.go Fix setting homepage URL in repo create 2020-03-09 12:53:41 +01:00