================
@@ -199,6 +199,9 @@ class CommandObjectDiagnosticsReport : public
CommandObjectParsed {
for (const std::string &file : report->attachments.files)
out << " [ ] " << file << "\n";
}
+ out << "Complete the report before sharing it:\n";
+ out << " [ ] Replace the placeholder title with a descriptive one\n";
+ out << " [ ] Answer the questions\n";
----------------
JDevlieghere wrote:
> IIUC, those would be printed to the debugger output and the user could
> completely dismiss them making the bug report low quality.
Yes, that covers the unenforceable part, but those bugs are also easy for us to
ignore.
> I think adding a
> [.github/ISSUE_TEMPLATE](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)
> would be more useful here.
I like that idea, but remember that this mechanism supports multiple backends,
not just GitHub.
Let me know if you feel strongly enough about omitting them here. Personally, I
think it's a low-cost reminder to fill out the questions and takes away
plausible deniability, while admittedly being unenforceable. I think the latter
can potentially be handled by the different "back ends" like Github through an
issue template.
https://github.com/llvm/llvm-project/pull/213173
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
