cli/context
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
..
blank_context.go Merge branch 'master' into repo-fork 2020-03-03 15:40:54 -06:00
config_file.go Extract common interface for a GitHub Repository 2020-01-22 22:44:46 +01:00
config_file_test.go Eliminate package-level state in git remote parsing 2019-10-25 21:48:25 +02:00
config_setup.go Add back comments explaining OAuth app credentials 2020-02-18 19:31:18 +01:00
config_success.go Restyle auth page 2020-01-22 14:45:31 -08:00
context.go Creating a PR now always prioritizes an existing fork as a push target 2020-03-19 16:04:23 +01:00
remote.go Fix parsing non-GitHub remotes 2020-01-28 19:51:44 +01:00
remote_test.go Creating a PR now always prioritizes an existing fork as a push target 2020-03-19 16:04:23 +01:00