cli/command
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
..
completion.go Improve completion docs 2020-03-05 09:34:05 +01:00
completion_test.go Add support for PowerShell completion 2020-03-05 09:33:49 +01:00
issue.go Merge branch 'master' into pr-count 2020-03-18 09:26:05 -07:00
issue_test.go Merge branch 'master' into pr-count 2020-03-18 09:26:05 -07:00
pr.go Merge branch 'master' into pr-count 2020-03-18 09:26:05 -07:00
pr_checkout.go Removed explicit capacity in slice initialization 2020-02-26 15:44:52 +01:00
pr_checkout_test.go add CmdStubber 2020-03-13 15:12:09 -05:00
pr_create.go Creating a PR now always prioritizes an existing fork as a push target 2020-03-19 16:04:23 +01:00
pr_create_test.go Creating a PR now always prioritizes an existing fork as a push target 2020-03-19 16:04:23 +01:00
pr_test.go Merge branch 'master' into pr-count 2020-03-18 09:26:05 -07:00
repo.go Implement review comments 2020-03-17 20:05:53 +03:00
repo_test.go add CmdStubber 2020-03-13 15:12:09 -05:00
root.go Implement review comments 2020-03-17 20:05:53 +03:00
root_test.go Fix gh version printing the correct changelog link 2020-01-29 16:03:10 +01:00
testing.go cleanup 2020-03-13 15:14:32 -05:00
title_body_survey.go review feedback 2020-03-16 15:32:35 -05:00