Sam Coe

This is a good idea, only thing that I think we should change would be the name of the `--force` flag as it does not seem descriptive enough to me....

@waldyrious Thank you for the feedback, I can understand how the messaging can be confusing. There is definitely room for improvement in the `pr create` messaging and we will take...

@heaths When implementing `pr checks` we purposefully wanted to prioritize the status and URL so that a user could easily bring up a specific check in their browser (see [here](https://github.com/cli/cli/blob/5f52a1d9643e901ebeff8660b008f22c712e75ce/utils/table_printer.go#L162)...

@anglinb You can use `gh config get oauth_token -h github.com` to retrieve the auth token without any other output text.

This might be a bit of feature creep but just wanted to chime in here since `search issues` and `search prs` just landed that we should extend the `isBot` export...

@randaz81 I think that it makes sense to support retrieving the repo's topics when using the `--json` flag. Going to open this up for contributions.

@alex-petrov-vt You are correct, the `repo list` already supports `repositoryTopics` json field. Going to close this as complete.

@RCheesley When setting up the `upstream` remote we use your configured `git_protocol` setting to determine the protocol to use for the remote URL. When you run `gh config get git_protocol...

@RCheesley I didn't catch this earlier but in your logs where it results in inconsistent remotes it has an error message. ``` error: remote upstream already exists. exit status 3...

@mntlty We discussed this offline as a team, with the still unknowns around the performance impact of the `mergeable` field on GHES and no easy way from the code to...