每个分支的github脆弱依赖项 [英] github vulnerable dependencies per branch

查看:68
本文介绍了每个分支的github脆弱依赖项的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我看来,您只能在 master 分支上看到易受攻击的依赖项。我将警报中提到的那些问题固定在一个单独的分支上,并希望检查实际上脆弱的依赖项是否已修复,所以我真正需要的是能够检查特定分支的警报,这可以做到吗?

It seems to me that you can only see the vulnerable dependencies on the master branch. I fixed those mentioned in the alert on a separate branch and want to check if in fact the vulnerable dependencies are fixed, so what I really need is to be able to check the alert for the specific branch, can this be done?

推荐答案

可能仅对默认分支有效(通常为 master ,但您可以更改)。

如果您尚未准备好将修订合并到存储库的默认分支,则一种解决方法是将该分支推送到默认分支(同样,通常新专用(和临时)存储库的> master )分支,只是为了检查在该新存储库上是否检测到任何新警报。

If you are not ready to merge your fix to the default branch of your repo, one workaround would be to push that branch to the default (again, usually master) branch of a new dedicated (and temporary) repository, just to check if any new alerts are detected on that new repo.

这篇关于每个分支的github脆弱依赖项的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆