Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GitHub] User should be able to select cloning ways when copying clone command #15749

Closed
sushichan044 opened this issue Dec 8, 2024 · 4 comments · Fixed by #15818
Closed
Labels
extension: github Issues related to the github extension extension Issues related to one of the extensions in the Store feature request New feature or improvement

Comments

@sushichan044
Copy link
Contributor

sushichan044 commented Dec 8, 2024

Extension

https://www.raycast.com/raycast/github

Description

Currently, commands copied by the Copy Clone Command are always for the HTTPS protocol.
We could consider changing this so that users can set their preferences for https/ssh in the settings,
allowing them to choose how they want commands copied.

Who will benefit from this feature?

Users prefers ssh protocol when execute git clone

Anything else?

It might be nice to add an option to use the GitHub CLI as well as the UI on github.com
スクリーンショット 2024-12-08 19 34 02

@sushichan044 sushichan044 added extension Issues related to one of the extensions in the Store feature request New feature or improvement labels Dec 8, 2024
@raycastbot raycastbot added the extension: github Issues related to the github extension label Dec 8, 2024
@raycastbot
Copy link
Collaborator

raycastbot commented Dec 8, 2024

Thank you for opening this issue!

🔔 @thomaslombart @unnamedd @tonka3000 @khasbilegt @pernielsentikaer @loxygenK @oilbeater @LunaticMuch @aeorge @daquinoaldo @peppy @aeither @marcotf @qeude @nesl247 @xilopaint @antonengelhardt @bangerang @wottpal @LitoMore @d-mitrofanov-v @j3lte @jfkisafk @vlasischar @JavaLangRuntimeException @shyakadavis you might want to have a look.

💡 Author and Contributors commands

The author and contributors of raycast/github can trigger bot actions by commenting:

  • @raycastbot close this issue Closes the issue.
  • @raycastbot close as not planned Closes the issue as not planned.
  • @raycastbot rename this issue to "Awesome new title" Renames the issue.
  • @raycastbot reopen this issue Reopens the issue.
  • @raycastbot assign me Assigns yourself to the issue.
  • @raycastbot good first issue Adds the "Good first issue" label to the issue.
  • @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

@sushichan044
Copy link
Contributor Author

sushichan044 commented Dec 8, 2024

I am trying to change the code to address this issue.
But, I need to create a PR to update gql schema first
because I found many differences due to the GitHub schema change when I did the GraphQL codegen.

@sushichan044 sushichan044 changed the title [GitHub] User can select git protocol when copying clone command [GitHub] User should be able to select ways when copying clone command Dec 8, 2024
@sushichan044 sushichan044 changed the title [GitHub] User should be able to select ways when copying clone command [GitHub] User should be able to select cloning ways when copying clone command Dec 8, 2024
@jfkisafk
Copy link
Contributor

I am trying to change the code to address this issue. But, I need to create a PR to update gql schema first because I found many differences due to the GitHub schema change when I did the GraphQL codegen.

@sushichan044 I think this is expected. The graphql client is anyways generated so feel free to include your fix for this issue in the PR too.

@sushichan044
Copy link
Contributor Author

@jfkisafk
Indeed, submitting a PR only to regenerate and wait is a little bothersome.
Thanks for the advice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension: github Issues related to the github extension extension Issues related to one of the extensions in the Store feature request New feature or improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants