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

[#1755] SSH key management (gh ssh-key list) #1862

Open
wants to merge 9 commits into
base: trunk
from
Open

Conversation

@edualb
Copy link

edualb commented Sep 20, 2020

Command gh ssh-key list implemented.

This feature request can be accessed by #1755 tag.

Command gh ssh-key list - That shows all of the currently SSH-KEY and names.
Test coverage 98%+

@edualb

This comment has been minimized.

Copy link
Author

edualb commented on 3c1f0a9 Sep 20, 2020

Do you suggest anything that I can identify the test? I didn't like the id either, but it was the way that I found it.

[Edit]
I noticed that the project uses testify lib, I will implement with this approach.

This comment has been minimized.

Copy link
Author

edualb replied Sep 20, 2020

The id was removed in ffbef3a and 9291212(removed comments only).

If the comment is about the entire TestCmdList, I did it based on status_test.go.

package key

import (
cmdList "github.com/cli/cli/pkg/cmd/ssh-key/list"

This comment has been minimized.

@TaherAltay TaherAltay mentioned this pull request Sep 20, 2020
Copy link
Member

mislav left a comment

Hi, thank you for the thorough implementation! The code looks solid at cursory glance.

However, I won't be fully reviewing this PR nor approving it at the moment because, per our CONTRIBUTING policy, we currently don't accept PRs for features that our team hasn't discussed and explicitly approved. Right now, we haven't reached a decision about ssh-key management being included in gh.

In the meantime, you may use your fork or gh api to manage ssh-keys. 🙇

@edualb
Copy link
Author

edualb commented Sep 21, 2020

@mislav Alright, no problem. I have learned a lot implementing this feature, thank you for your recognition 😄

So, this PR will be closed? Or, can we wait for the team decision?

@mislav
Copy link
Member

mislav commented Sep 21, 2020

We haven't done feature prioritization yet for a post-1.0 release, so let's keep this open until we do, if you don't mind (a couple of weeks tops).

@vilmibm vilmibm added the community label Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.