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
We have a gh edu update command (Maybe it should be called upgrade instead). We can reuse this command to also update plugins, not only the cache.
Also, gh cli doesn't have this behavior so it could be unintuitive.
We have a gh edu update command (Maybe it should be called upgrade instead). We can reuse this command to also update plugins, not only the cache.
Also, gh cli doesn't have this behavior so it could be unintuitive.
Agree. May be gh edu update can be multi-command like:
gh edu update cache # updates the cache
gh edu update plugins # updates the plugins
etc.
program.command("update").option("-c, --cache","Update your cache").option("-p, --plugins","Update your plugins").option("-a, --all","Update all").description("Update your configuration").action((options)=>{update(options);})
In any case an user can always update manually, so may be this requirement is not so important and can be delayed
What do you think about this @GGCristo ?
We will keep of the plugins installed with
gh edu install plugin
inside theconfig.json
file and then ...When called without arguments:
should install (or update?) the plugins specified in file
config.json
.The text was updated successfully, but these errors were encountered: