Skip to main content

Electron 中的问题

¥Issues In Electron

如何对问题做出贡献​

¥How to Contribute to Issues

对于任何问题，个人基本上可以通过三种方式做出贡献：

¥For any issue, there are fundamentally three ways an individual can contribute:

  1. 通过打开问题进行讨论：如果你认为在 Electron 中发现了新错误，你应该通过在 electron/electron 问题跟踪器 中创建新问题来报告该错误。

    ¥By opening the issue for discussion: If you believe that you have found a new bug in Electron, you should report it by creating a new issue in the electron/electron issue tracker.

  2. 通过帮助对问题进行分类：你可以通过提供辅助详细信息（演示错误的可重现测试用例）或提供解决问题的建议来完成此操作。

    ¥By helping to triage the issue: You can do this either by providing assistive details (a reproducible test case that demonstrates a bug) or by providing suggestions to address the issue.

  3. 通过帮助解决问题：这可以通过证明问题不是错误或已修复来完成；但更常见的是，通过打开一个拉取请求，以具体且可审查的方式更改 electron/electron 中的源代码。

    ¥By helping to resolve the issue: This can be done by demonstrating that the issue is not a bug or is fixed; but more often, by opening a pull request that changes the source in electron/electron in a concrete and reviewable manner.

寻求一般帮助​

¥Asking for General Help

Electron 网站 有一个资源列表，用于获取编程帮助、报告安全问题、做出贡献等。请仅使用问题跟踪器来查找错误！

¥The Electron website has a list of resources for getting programming help, reporting security issues, contributing, and more. Please use the issue tracker for bugs only!

提交错误报告​

¥Submitting a Bug Report

要提交错误报告：

¥To submit a bug report:

当在 electron/electron 问题跟踪器 中打开新问题时，用户将看到一个需要填写的模板。

¥When opening a new issue in the electron/electron issue tracker, users will be presented with a template that should be filled in.

如果你认为自己发现了 Electron 中的错误，请尽你所能填写模板。

¥If you believe that you have found a bug in Electron, please fill out the template to the best of your ability.

评估报告所需的两个最重要的信息是错误的描述和重新创建错误的简单测试用例。如果可以重现错误，则修复错误会更容易。

¥The two most important pieces of information needed to evaluate the report are a description of the bug and a simple test case to recreate it. It is easier to fix a bug if it can be reproduced.

参见 如何创建最小、完整且可验证的示例。

¥See How to create a Minimal, Complete, and Verifiable example.

对错误报告进行分类​

¥Triaging a Bug Report

公开问题涉及讨论是很常见的。一些贡献者可能有不同的意见，包括该行为是错误还是功能。这种讨论是整个过程的一部分，应该保持重点突出、有益且专业。

¥It's common for open issues to involve discussion. Some contributors may have differing opinions, including whether the behavior is a bug or feature. This discussion is part of the process and should be kept focused, helpful, and professional.

既不提供额外背景也不提供支持细节的简洁响应既没有帮助，也不专业。对许多人来说，这样的回应令人恼火且不友好。

¥Terse responses that provide neither additional context nor supporting detail are not helpful or professional. To many, such responses are annoying and unfriendly.

我们鼓励贡献者协作解决问题并帮助彼此取得进展。如果你遇到你认为无效或包含不正确信息的问题，请通过其他支持上下文解释为什么你有这种感觉，并愿意相信你可能是错的。通过这样做，我们通常可以更快地达到正确的结果。

¥Contributors are encouraged to solve issues collaboratively and help one another make progress. If you encounter an issue that you feel is invalid, or which contains incorrect information, explain why you feel that way with additional supporting context, and be willing to be convinced that you may be wrong. By doing so, we can often reach the correct outcome faster.

解决错误报告​

¥Resolving a Bug Report

大多数问题都是通过提出拉取请求来解决的。打开和审查拉取请求的过程与打开和分类问题的过程类似，但带有必要的审查和批准工作流，以确保提议的更改满足 Electron 项目的最低质量和功能指南。

¥Most issues are resolved by opening a pull request. The process for opening and reviewing a pull request is similar to that of opening and triaging issues, but carries with it a necessary review and approval workflow that ensures that the proposed changes meet the minimal quality and functional guidelines of the Electron project.