-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Show Outdated GitHub Actions Dependencies #928
Comments
To be honest I am not sure if this is the responsibly for this cli 🤔.
As far as I know the cli is more like "github for the terminal". Since
github web doesn't display this information and there is even no api for
this I would think this should be a github (web) request first.
…On Fri, May 15, 2020, 2:58 AM Charlie Fish ***@***.***> wrote:
Describe the feature or problem you’d like to solve
There is no good way currently to view outdated GitHub Actions
Dependencies. In npm this can be done with npm outdated. It would be
awesome if there was a way to do this in the GitHub CLI to easily view
which GitHub Actions Dependencies are outdated and potentially even update
them automatically.
Proposed solution
Potentially something like: gh actions outdated. This would then look
inside each workflow and find all the actions that are outdated and list
them. Similar to how npm outdated works.
I'm unsure if the syntax gh actions outdated makes sense, and there
should probably be more discussion around the best command for this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#928>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOBQ65OQPL5DO33LJV2KTDRRSHSPANCNFSM4NBE3BCA>
.
|
@StefMa So this could truly go either way IMO. I can see how it'd make sense to have an API or something like this first. However, the comparison is to npm, which has When I realized the need for this feature, the first thing I thought about is if the GitHub CLI had this. It didn't. So I created an issue. I for sure didn't think through what the best interface is for this and how exactly it'd work. But to me, it is meaningful that my first thought was to integrate this into the GitHub CLI due to the similarity of So although it was on a whim, I do think it's valuable to think off the top of your head sometimes, and that lead to this issue. |
It's certainly an interesting proposal, thank you. We've been also getting other feature requests to support Actions, such as exposing an interface to repository Secrets. None of the Actions work is on our roadmap yet, but we might factor these ideas in our future planning. |
Dependabot should provide information about actions you are referencing in your workflows that have new versions. |
@chrispat Can I run dependabot locally from the command line? |
Having dependabot baked into the cli would be a great idea. examples |
Describe the feature or problem you’d like to solve
There is no good way currently to view outdated GitHub Actions Dependencies. In npm this can be done with
npm outdated
. It would be awesome if there was a way to do this in the GitHub CLI to easily view which GitHub Actions Dependencies are outdated and potentially even update them automatically.Proposed solution
Potentially something like:
gh actions outdated
. This would then look inside each workflow and find all the actions that are outdated and list them. Similar to hownpm outdated
works.I'm unsure if the syntax
gh actions outdated
makes sense, and there should probably be more discussion around the best command for this.The text was updated successfully, but these errors were encountered: