Tyler McGoffin

🤔 This seems like a reasonable bit of behavior, but I'm a bit hung up on this possibly being a bit outside the scope of `gh` because renaming your local...

## Design ```shell # When the user doesn't specify anything $ gh repo rename ? Rename to: ? Would you also like to rename the local directory to the same...

> Sounds reasonable to me > > I would also recommend documenting that rename cannot transfer ownership, `` does _not_ mean `$owner/$repo` like it does in most gh commands `gh...

Gotcha. So for many commands, we assume `$owner` based on your current directory, similarly to what we did here. You can often specify `$owner/$repo` if trying to perform an operation...

> Is this possible to implement? When using `gh repo rename` to change the folder name of the current repository, since you are inside that folder, you should encounter an...

> Here’s the [PoC](https://github.com/cli/cli/compare/trunk...benebsiny:cli:cli-9695) I made. I also did some research and found that when you run `gh repo rename`, the process's working directory is the folder you are trying...

Hello @k-obrien, thanks for submitting this. I've been able to reproduce what you've reported here with some additional search params: ``` $ gh search prs --repo=cli/cli --state=open --json repository,number,title,commentsCount --jq...

@wingleung, thanks for investigating this! I've reached out to the responsible team for more info 🙌

@k-obrien & @wingleung, I've confirmed with the owning team that there is, indeed, a 🐛. They'll be taking on the work to fix this, though I don't have an estimate...

Ah, good find! Had to do some real digging on this but I think the issue is coming from a [quirk in our markdown converter, kramdown,](https://kramdown.gettalong.org/syntax.html#tables) for the manual sites:...