如何禁用或忽略依赖性拉力请求?
我们希望使用Dispenabot了解更新的依赖关系,但是我们不希望Dispenabot自行创建拉动请求,并且不需要自动化构建(我们使用GitHub用于代码,Azure DevOps for Builds)。
文档中没有明确的提示( https://docs.github.com/en/code-security/depperabot/working-with-with-depparebot/automating-depparebot-with-with-with-github-actions ) 我们已经试图排除依赖关系分支,但这并不能以任何形式起作用。
# Azure DevOps Excludes
pr:
autoCancel: "true"
branches:
exclude:
- dependabot/*
- dependabot/**/*
我们还发现堆栈溢出上的提示将限制设置为0,但仍创建了PRS
version: 2
updates:
- directory: "/"
open-pull-requests-limit: 0
将Displabot用作信息源的可能性吗?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
转到安全 - > DiDeNTABOT - >配置 - >管理存储库漏洞设置。 (这应该将您带到 https://github.com/yourusername/yourusername/yourreponemettings/settings/settings/security_analysis“ /security_analysis 。)
启用了“依赖关系警报”设置,但请确保“ Disporabot版本更新”设置为 disabled 。
如果您先前启用了“ displabot版本更新”,则您将拥有
.github/disterabot.yml
repo中的文件,其目的是配置DiDeDabot的自动更新。要禁用它们,请删除distrabot.yml
。在图片中:
Go to Security -> Dependabot -> Configure -> Manage Repository Vulnerability Settings. (This should take you to a URL like https://github.com/yourusername/yourreponame/settings/security_analysis.)
Leave the "Dependabot alerts" setting enabled but ensure the "Dependabot version updates" setting is disabled.
If you've previously enabled "Dependabot version updates", you'll have a
.github/dependabot.yml
file in your repo, whose purpose is to configure Dependabot's automatic updates. To disable them, deletedependabot.yml
.In pictures:
You will now still be able to view security alerts about your dependencies on GitHub, but Dependabot will not open PRs for them.
默认情况下,
distrabot
将自动重置拉动请求以解决任何冲突。如果您希望手动处理合并冲突,则可以使用rebase-Strategy
选项禁用此功能。对于重列策略,使用
禁用
禁用自动重新启动。设置此选项还会影响该软件包管理器清单文件的安全更新的拉动请求,除非您使用
target-Branch
检查非默认分支上的版本更新。对于
rebase-Strategy
示例,By default,
Dependabot
will automatically reset pull requests to resolve any conflicts. If you prefer to handle merge conflicts manually, you can disable this feature with therebase-strategy
option.For rebase strategies, using
disabled
to disable automatic rebasing.Setting this option will also affect pull requests for security updates to this package manager's manifest file, unless you use
target-branch
to check for version updates on non-default branches.For
rebase-strategy
example,