{"meta":{"title":"分析和采纳用户反馈","intro":"Copilot Chat 可以增强将用户反馈合并到项目中的过程。","product":"GitHub Copilot","breadcrumbs":[{"href":"/zh/copilot","title":"GitHub Copilot"},{"href":"/zh/copilot/tutorials","title":"教程"},{"href":"/zh/copilot/tutorials/copilot-cookbook","title":"GitHub Copilot 指南"},{"href":"/zh/copilot/tutorials/copilot-cookbook/analyze-functionality","title":"分析功能"},{"href":"/zh/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback","title":"分析反馈"}],"documentType":"article"},"body":"# 分析和采纳用户反馈\n\nCopilot Chat 可以增强将用户反馈合并到项目中的过程。\n\n收集和采纳用户反馈对产品开发至关重要，但此过程可能具有挑战性。 开发人员和产品团队往往难以有效地分析用户反馈、确定优先级并根据反馈实施更改，同时又不影响现有工作流或引入新议题。\n\n## 分析用户反馈\n\n用户反馈可能会让人不知所措，而且可能很难确定应该对哪些反馈做出回应。\n\n### 示例方案\n\n假设你是常用开放源代码仓库的维护者。 由于社区非常投入你的project，因此他们经常提出问题以提供反馈。 他们还经常与未解决的问题互动。 你想对这些反馈做出回应，但不确定从何处着手。\n\n### 示例提示\n\n此示例假设使用标签来跟踪仓库中与用户反馈相关的议题。\n\n导航到存储库中的**问题**选项卡，然后键入：\n\n```copilot copy\nFind the issues with the feedback label that have the most reactions, and categorize them based on sentiment.\n```\n\n> \\[!TIP] 若要试用此提示，可以转到 [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) 存储库，该存储库使用标签跟踪功能请求并键入：`Find the issues with the feature-request label that have the most reactions, and categorize them based on sentiment.`\n\n### 示例响应\n\n> \\[!NOTE] 以下响应是示例。 Copilot Chat 的回答是不确定的，因此你可能会得到与这里所显示的不同的回答。\n\nCopilot 列出最有反应的问题，并为每个问题提供情绪分析。 在确定工作优先级时，可以利用此列表来做出更明智的决策。\n\n例如：\n\n```text\n1. [Feedback] CLI error messages are difficult to understand\n  * Issue URL: #321\n  * Reactions: 543\n  * Sentiment: Negative\n\n1. [Feedback] Add API to enable third party integration\n  * Issue URL: #210\n  * Reactions: 482\n  * Sentiment: Positive\n\n1. [Feedback] Shortcut for --with-token CLI option\n  * Issue URL: #426\n  * Reactions: 187\n  * Sentiment: Neutral to slightly positive\n```\n\n## 生成功能规范\n\n功能规范提供了开发计划，有助于在实施新功能之前进行沟通和协调。\n\n### 示例方案\n\n在这种情况下，你选择了一条要解决的用户反馈。 有人要求为现有的 CLI 选项提供快捷方式。 现在，你要为如何实现这一功能制定一个计划。\n\n### 示例提示\n\n此示例假定你是在咨询你使用 Copilot Chat 的同一存储库中的问题。\n\n```copilot copy\nWrite a feature specification for Issue #426.\n```\n\n### 示例响应\n\n> \\[!NOTE] 以下响应是示例。 Copilot Chat 的回答是不确定的，因此你可能会得到与这里所显示的不同的回答。\n\nCopilot 生成一个功能规范，如下所示。\n\n```text\n# Feature Specification for Issue #426: Shortcut for --with-token CLI option\n\n## Description:\nCurrently, the --with-token option is used to pass in a token to commands. Typing --with-token each time is cumbersome. This feature proposes a new flag -wt as a shortcut to quickly specify the --with-token option when running various commands.\n\n## Problem:\nTyping --with-token repeatedly is time-consuming and inconvenient for users who frequently use this option.\n\n## Solution:\nIntroduce a new flag -wt that serves as a shortcut for the --with-token option.\n\n## Feature Details:\n\n### 1. Flag Introduction:\n-wt will be introduced as a shorthand for --with-token.\nUsage: <command> -wt <token>\n\n### 2. Commands Affected:\nAll commands that currently support the --with-token option.\n\n### 3. Backward Compatibility:\n- The existing --with-token option will continue to work as before.\n- No existing functionality will be removed or altered.\n\n### 4. Documentation:\n- Update documentation to include the new -wt flag.\n- Provide examples and usage scenarios for the new flag.\n\n### 5. Testing:\n- Ensure thorough testing of the -wt flag across various commands.\n- Test cases should include:\n  - Valid and invalid tokens.\n  - Interaction with other options.\n  - Ensuring no regression in current --with-token functionality.\n\n## Benefits:\n- Improved user experience by reducing the amount of typing required.\n- Streamlined command execution for users who frequently use the --with-token option.\n\n## Potential Risks:\nMinimal risk as this feature is an addition and does not alter existing functionality.\n```\n\n## 延伸阅读\n\n* [GitHub Copilot 对话助手的提示设计](/zh/copilot/concepts/prompting/prompt-engineering)\n* [使用 GitHub Copilot 的最佳做法](/zh/copilot/get-started/best-practices)"}