[BUG] 'Incorrect type. Expected "array".' w/ "✅ Label bug reports"

[classicrocker883]

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

even though it seems to work fine how it is, I do receive an error/warning (red squiggles) with ISSUE_TEMPLATE/bug_report.yml.

name: 🪲 Report a bug
description: Create a bug report to help improve Marlin Firmware
title: "[BUG] (bug summary)"
labels: 'Bug: Potential ?'
body:
  - type: markdown

specfically this line labels: 'Bug: Potential ?'
it says 'Incorrect type. Expected "array".' then gives a link for the correct syntax.

based on other examples, the corrected code should be

labels: ["Bug: Potential ?"]

it does help if you ever wanted to include other labels.

Bug Timeline

11/29 - ✅ Label bug reports

Expected behavior

should not have an error

Actual behavior

error in form of red squiggles

Steps to Reproduce

No response

Version of Marlin Firmware

current bugfix

Printer model

No response

Electronics

No response

LCD/Controller

No response

Other add-ons

No response

Bed Leveling

None

Your Slicer

None

Host Software

None

Don't forget to include

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[thisiskeithb]

This works fine, but please submit a PR if you'd like to see this changed.

We also don't have brackets for Feature Request tags:

Marlin/.github/ISSUE_TEMPLATE/feature_request.yml

Line 4 in b17d3d3

labels: 'T: Feature Request'

[classicrocker883]

This works fine, but please submit a PR if you'd like to see this changed.

yes it does seem to "work", but do you still see the error squiggles within VScode?

[thisiskeithb]

yes it does seem to "work", but do you still see the error squiggles within VScode?

No.

[thisiskeithb]

I don't think brackets are required for a single label. Especially since it works fine without them.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.