Usage is based on the extension https://github.com/mislav/gh-delete-repo .

To confirm deletion user types the full repo name, or passes in --confirm flag (for scripting purposes)

@vilmibm

It'd be great to notice when the API call 403s and suggest that the user run gh auth refresh -sdelete_repo to fix it; for all other HTTP error status codes, just printing the error as is done now is fine.

I originally had this and @mislav suggested that it wasn't necessary. He said he is working on general scope error handling. Should I put it in for now?

@mislav Your code doesn't handle this case, hence why I specifically asked meiji163 yesterday to handle the 403 in the way he did; I don't see a way around the explicit error handling. Do you disagree that we should suggest the scope refresh in cases like this where the 403 doesn't have a missing scopes header?

sorry for my confusion: I read in the error handling PR that this case wouldn't be handled and then, locally, didn't realize that trunk hadn't been merged into this PR so I didn't see the new behavior. Sorry for all the churn.

Since @mislav 's final change request was addressed, I'm going to go ahead and merge this.

Thanks for adding the feature 🥳🥳🎉🎉

Add gh repo delete command. Fixes #3625