You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that an increasing number of our operations rely on the gh auth status call to retrieve the current user's username and then making calls based on that. I think this is pretty inefficient, because we have to manually execute the command and then parse the string which could be None.
My initial thought is to store this information when the user first initializes Git-Mastery, storing it under the .gitmastery.json file.
There may be other use cases, but this is the primary one I can think of right now.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Based on git-mastery/exercises#122
I noticed that an increasing number of our operations rely on the
gh auth statuscall to retrieve the current user's username and then making calls based on that. I think this is pretty inefficient, because we have to manually execute the command and then parse the string which could beNone.My initial thought is to store this information when the user first initializes Git-Mastery, storing it under the
.gitmastery.jsonfile.There may be other use cases, but this is the primary one I can think of right now.
Beta Was this translation helpful? Give feedback.
All reactions