🔧 config: fix bug template

[LazyYuuki]

Describe Your Changes

Fixes Issues

• Closes #
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Fix and simplify the bug report template in 1-bug-report.md.

• Template Changes:
  • Remove comment about Jan version in 1-bug-report.md.
  • Simplify steps to reproduce section in 1-bug-report.md.
  • Update logs path description in 1-bug-report.md to "Setting -> General -> Data Folder -> App Logs".
  • Change projects field format in 1-bug-report.md from array to string.

^{This description was created by for 5dc9073. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 5dc9073 in 1 minute and 53 seconds. Click for details.

• Reviewed 37 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/ISSUE_TEMPLATE/1-bug-report.md:6

• Draft comment:
  The 'projects' field was changed from a list (["menloresearch/30"]) to a bare string (menloresearch/30). Verify that this is intentional. A list may be more extensible if multiple projects need to be assigned in the future.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

2. .github/ISSUE_TEMPLATE/1-bug-report.md:16

• Draft comment:
  The Steps to Reproduce section now only contains '1.' without further guidance. Consider providing placeholder text or brief instructions to encourage users to detail the reproduction steps.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 20% <= threshold 50% This comment is asking the PR author to provide more information in a section that is likely part of a template or documentation. It doesn't suggest a specific code change or improvement, and it seems to be more about ensuring completeness of information rather than addressing a specific code issue.

3. .github/ISSUE_TEMPLATE/1-bug-report.md:9

• Draft comment:
  The 'Jan Version' section and its detailed comment were removed in favor of a concise version line. Ensure that this change still provides sufficient context for users regarding the version information.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50% None

4. .github/ISSUE_TEMPLATE/1-bug-report.md:19

• Draft comment:
  The log file path instruction was updated. Confirm that the new guidance ('Setting -> General -> Data Folder -> App Logs') accurately reflects the application's current log location.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm the accuracy of the new log file path instruction. It is essentially asking for confirmation of intention, which violates the rule against asking the PR author to confirm their intention or to ensure the behavior is intended.

5. .github/ISSUE_TEMPLATE/1-bug-report.md:19

• Draft comment:
  There seems to be a minor typographical issue in the log location comment: it currently reads "Setting -> General -> Data Folder -> App Logs". Should it be "Settings -> General -> Data Folder -> App Logs"?
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is a very minor typo fix. While technically correct, it doesn't impact functionality - users will still understand the path. The rules specifically say not to make comments that are obvious or unimportant. This seems like an extremely minor nitpick that doesn't warrant a comment. The path might be technically incorrect and could confuse some users. Documentation accuracy can be important. While accuracy is good, this is such a minor issue that it doesn't meet our bar for commenting. Users will still find the logs successfully. Delete this comment as it's too minor and doesn't meet our threshold for necessary changes.

Workflow ID: wflow_KAEIVs8Sc2bQKDKT

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[Minh141120]

LGTM!