Oh I think we’ve started the extend phase. Did you notice they put out their own GitHub specific git cli? And they removed ssh links and replaced them with links specific to their cli
At least in a couple of projects i just checked the SSH link is still there, between the HTTPS and the GitHub CLI command.
Only if you are logged in. It used to be there always.
Are you sure about that? I certainly don't recall that, and it seems like it would be a bad UX idea anyway: you can't clone a repo via SSH without having an account (and a pubkey registered), so showing the SSH string to people who aren't logged in seems counterproductive.
`gh`is great for handling pull requests and other GitHub specifics. I still use `git` for everything else, so I dunno how much it does, but it makes sense if `gh` overlaps with some `git` commands to round out the tool.
You've been lured by the "extend" phase.
Isn't GH's PR some awful sugar around the concept of merging a patchset?
`hub` had the same functionality and could be used either standalone or integrated with git so `git hub` ran hub commands to e.g. manage a pull request.
gh is just trying to get you to stop using git itself
The SSH links aren't replaced by the gh links, the gh links are just an additional option.
Or actually, they aren't replaced everywhere: the "Code" tab still has HTTPS and SSH in addition to the GitHub CLI; the "Pull Request" tab has only the CLI.