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

Use gcrane.Keychain for not only crane-inherit commands but also gcrane-specific commands. #880

Conversation

FGtatsuro
Copy link
Contributor

@FGtatsuro FGtatsuro commented Dec 19, 2020

#845 introduces gcrane.Keychain.

This PR uses gcrane.Keychain for not only crane-inherit commands(ex. pull) but also gcrane-specific commands(gc/ls).

@codecov-io
Copy link

Codecov Report

Merging #880 (a976d50) into master (8b4c3b5) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #880   +/-   ##
=======================================
  Coverage   74.33%   74.33%           
=======================================
  Files         107      107           
  Lines        4523     4523           
=======================================
  Hits         3362     3362           
  Misses        661      661           
  Partials      500      500           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b4c3b5...a976d50. Read the comment docs.

Copy link
Collaborator

@jonjohnsonjr jonjohnsonjr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, thanks!

@jonjohnsonjr jonjohnsonjr merged commit d29eb11 into google:master Dec 21, 2020
@FGtatsuro FGtatsuro deleted the use_gcrane_keychain_for_specific_commands branch December 21, 2020 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants