Hi, thank you for the feature request. This would have been a good addition to the CLI; unfortunately the API that we use does not support choosing the fork name at fork time: https://docs.github.com/en/rest/reference/repos#create-a-fork

You can call an additional command to rename your fork with gh repo rename -R owner/my-project new-fork-name, but that won't help if there is already an unrelated owner/my-project repository at the time of forking somebody-else/my-project. It looks like name clashes are unavoidable until the platform gets the feature to choose the new name in the API request.

Update: I just tested and it looks like on name collisions, the new fork in your account will have a number appended to the forked repo in case you already have a repository matching the name of the repository you're forking. The fork will get named myowner/repo-2 in case you already have myowner/repo. Since this works without erroring out, GitHub CLI could actually take the desired fork name as argument and rename the repository post-forking! Contributions welcome 👍

Tip: see pkg/cmd/repo/rename for an existing repo-renaming implementation that could be borrowed from or reused

@mislav I tried fixing this by the approach you mentioned i.e renaming it after forking. I've opened a PR #4886. Do give feedback on what changes can be done here thank you :)