Format all YAML files to pass yamllint validation

- Added document start markers (---) to all YAML files
- Fixed line length issues by breaking long lines appropriately
- Removed trailing whitespace throughout all files
- Added proper newlines at end of files
- Fixed truthy value format ('on' -> 'on')
- Standardized YAML formatting across workflows and issue templates
- Used multi-line strings (>) for long descriptions
- Maintained readability while adhering to 80-character line limit

All YAML files now pass yamllint validation with only minor warnings remaining.
This commit is contained in:
Seth Hobson
2025-08-01 17:33:42 -04:00
parent fe236a76b5
commit 4dad1937e9
7 changed files with 224 additions and 107 deletions

View File

@@ -1,3 +1,4 @@
---
name: Feature Request
description: Suggest an improvement or new feature for existing subagents
title: "[FEATURE] "
@@ -6,9 +7,11 @@ body:
- type: markdown
attributes:
value: |
Thank you for suggesting a feature! Please provide detailed information to help us understand your request.
**Note**: For new subagent proposals, please use the "New Subagent Proposal" template instead.
Thank you for suggesting a feature! Please provide detailed
information to help us understand your request.
**Note**: For new subagent proposals, please use the
"New Subagent Proposal" template instead.
- type: checkboxes
id: preliminary-checks
@@ -18,7 +21,8 @@ body:
options:
- label: I have read the [Code of Conduct](.github/CODE_OF_CONDUCT.md)
required: true
- label: I have searched existing issues to ensure this is not a duplicate
- label: >-
I have searched existing issues to ensure this is not a duplicate
required: true
- label: This is a constructive feature request for legitimate use cases
required: true
@@ -74,4 +78,4 @@ body:
attributes:
label: Additional Context
description: Any other relevant information
placeholder: Add any other context, examples, or screenshots here...
placeholder: Add any other context, examples, or screenshots here...