Repository navigation
Fix markdown formatting in feature request template - #814
Conversation
Updated markdown syntax for the feature request template.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
â WordPress Plugin Check Report
ð ReportAll checks passed! No errors or warnings found. ðĪ Generated by WordPress Plugin Check Action âĒ Learn more about Plugin Check |
Codecov Reportâ
All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #814 +/- ##
==========================================
Coverage 75.50% 75.50%
Complexity 2086 2086
==========================================
Files 99 99
Lines 8626 8626
==========================================
Hits 6513 6513
Misses 2113 2113
Flags with carried forward coverage won't be shown. Click here to find out more. â View full report in Codecov by Harness. ð New features to boost your workflow:
|
dkotter
left a comment
There was a problem hiding this comment.
So looking at the error message here: https://github.com/WordPress/ai/blob/develop/.github/ISSUE_TEMPLATE/feature_request.yml:
body[4]: options[0]: label must be of type String and cannot be empty
I don't think this will fix that. I think we need to add quotes around the last checkbox label. I can push a change to this PR for that
âĶget interpreted as a boolean
Updated markdown syntax for the feature request template.
What?
I'm getting super frustrated with trying to fix this darn feature request issue template. I think? hope? maybe fixed the issue template by forcing it into a string, but the bug template isn't this way so who knows what's going on with GitHub's issue templates. ðĪ·ðž
Why?
How?
Use of AI Tools
AI assistance: none, though maybe I should have because this is like attempt 3 of trying to fix this.
Testing Instructions
Screenshots or screencast
Changelog Entry