英文:
Why do some dependabot PRs not contain any information?
问题
我正在撰写一篇关于Dependabot PRs及其与开发人员互动的论文。为此，我已经找到了一些Dependabot PRs的示例进行分析。Dependabot能够提供的最重要信息包括“Changelog”、“Release notes”和“Commits”部分，以及兼容性启发式。但在某些情况下，其中一项或多项内容可能会缺失（例如，此PR 中未提供任何内容）。这是为什么呢？是什么决定了PR中包含哪些部分？
另外，在上述示例中，为什么即使运行的测试结果明确，兼容性启发式仍然被标记为未知？
英文:
I am writing a paper on dependabot PRs and its interaction with developers. To this extent I have found some examples of dependabot PRs to analyse. The most information dependabot can provide you with is "Changelog", "Release notes" and "Commits" sections, plus the compatibility heuristic. But in some cases one or more of these are missing (e.g. this PR where none of it is presented). Why is it so? What defines which of these sections are present in the PR?
Also, in the example given above, why is the compatibility heuristic tagged as unknown even if the tests that were ran have clear results?
答案1
得分: 2
我是GitHub的Dependabot产品经理。对于你的问题，答案归结为“我们对不同生态系统的支持不同”。每个生态系统都有不同的方式来发布每个版本升级的变更日志/提交信息，有些更具程序性，这可能会让我们更容易或更难提取所需的信息来填充这些字段。
如果在撰写论文过程中对Dependabot有任何进一步的问题，请随时通过carogalvin（at）github.com给我发电子邮件，我将很乐意帮助您。
英文:
I'm the PM for Dependabot at GitHub. The answer to your question comes down to "our support for different ecosystems is different." Each ecosystem has a different way that they publish the changelog/commits information for each version bump, and some are more programmatic than others, which can make it easier or harder for us to pull the info needed to populate those fields.
If you have any further questions about Dependabot as you are working on your paper, please feel free to email me at carogalvin(at)github.com and I'd be happy to help.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论