Replies: 2 comments 3 replies
-
I can see the value in adding this feature and I've wanted something like this myself. I've been imagining it as a session-level environment variable such as However, we don't want to rush adding cache to other commands too fast because with caching there comes a problem of how does the user handle cache expiration. We don't have a great story for this yet: #4994 |
Beta Was this translation helpful? Give feedback.
-
@bewuethr / @mislav |
Beta Was this translation helpful? Give feedback.
-
It would be great if a few other commands had a
--cache
option with a similar behaviour togh api
(doesn't hit the API as long as the cache is valid); two examples I've encountered where this would be beneficial:gh workflow view 123 --yaml
for many workflows and running multiple checks on them; I wouldn't have to care if the workflow has been fetched already or notgh pr list
with a complicated and expensive--search
query that I want to run multiple times for different parameters; currently, I have to store the result locally before running queries, i.e., can't leverage--jq
Beta Was this translation helpful? Give feedback.
All reactions