We should support links inside GitHub issue

[h1alexbel]

as we outlined here, we should present all the hidden information in links and source tree in the text, so that we can operate with this content, parse it in deterministic manner, and present it to the language model

[github-actions]

@h1alexbel thanks for the report, but here some unclear moments:

• The bug report lacks a clear and concise description of the problem or bug. It only states what should be added or improved without specifying the current issue.
• The bug report does not provide any background information or steps to reproduce the issue, which makes it difficult for developers to understand and fix the problem.
• The bug report includes a link to an external resource but does not summarize the content of the link. It would be better to include a summary of the linked information in the report itself to avoid reliance on external sources.
• The bug report uses informal language, such as "we should," which may not be clear to all readers. It would be more effective to use imperative statements to describe the expected behavior, like "Add support for links."
• The bug report does not prioritize the issue, which makes it difficult for developers to know how to allocate resources. Consider including a priority label, such as "low," "medium," or "high."
• The bug report does not include any labels or tags to categorize the issue, which can make it difficult for developers to find and work on related issues.

Please fix the bug report in order it to get resolved faster.
Analyzed with Phind/Phind-CodeLlama-34B-v2