Conversation
Replaces Markdown-based issue templates with YAML-based issue forms. This update provides a more structured and user-friendly experience for submitting issues. Signed-off-by: Ryan Johnson <ryan.johnson@broadcom.com>
There was a problem hiding this comment.
Pull request overview
This PR modernizes the issue reporting experience by replacing Markdown-based issue templates with YAML-based GitHub issue forms. The update provides a more structured, user-friendly interface for submitting bugs, enhancement requests, and documentation issues.
Changes:
- Removed legacy Markdown templates (
bug_report.mdandfeature_requests.md) - Added comprehensive YAML issue forms with structured fields and validation
- Introduced three template types: Bug Report, Enhancement Request, and Documentation
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
.github/ISSUE_TEMPLATE/bug_report.md |
Removed legacy Markdown bug report template |
.github/ISSUE_TEMPLATE/feature_requests.md |
Removed legacy Markdown feature request template |
.github/ISSUE_TEMPLATE/bug.yml |
Added structured YAML form for bug reports with version fields, builder/post-processor selection, and required information sections |
.github/ISSUE_TEMPLATE/enhancement.yml |
Added structured YAML form for enhancement requests with use cases, configuration examples, and references |
.github/ISSUE_TEMPLATE/docs.yml |
Added structured YAML form for documentation issues with detail and suggestion fields |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| id: vsphere-version | ||
| attributes: | ||
| label: vSphere Version | ||
| description: Provide the version of the VMware vSphere are using. |
There was a problem hiding this comment.
Grammar error: "the VMware vSphere are using" should be "the VMware vSphere you are using". The word "you" is missing from the description.
| description: Provide the version of the VMware vSphere are using. | |
| description: Provide the version of the VMware vSphere you are using. |
| This project has a [Code of Conduct](https://github.com/vmware/packer-plugin-vsphere/blob/main/CODE_OF_CONDUCT.md) | ||
| that all participants are expected to understand and follow. | ||
| options: | ||
| - label: I have read and agree to the project's Code of Conduct. |
There was a problem hiding this comment.
Inconsistent Code of Conduct checkbox label. The bug and documentation templates use "I have read and agree to the Code of Conduct" with a hyperlink, while this template uses "I have read and agree to the project's Code of Conduct" without a hyperlink in the label text. For consistency, the label should match the pattern used in the other templates and include the hyperlink directly in the label.
| description: >- | ||
| This project has a [Code of Conduct](https://github.com/vmware/packer-plugin-vsphere/blob/main/CODE_OF_CONDUCT.md) | ||
| that all participants are expected to understand and follow. |
There was a problem hiding this comment.
Inconsistent Code of Conduct description format. The bug and documentation templates use "The Code of Conduct applies to you when interacting with the community here on GitHub and contributing code" while this template has a different description format. For consistency across templates, consider using the same description text.
|
This functionality has been released in v2.1.0 of the plugin. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
1 similar comment
|
This functionality has been released in v2.1.0 of the plugin. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
|
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Summary
Replaces Markdown-based issue templates with YAML-based issue forms.
This update provides a more structured and user-friendly experience for submitting issues.
Type
fix: Bug Fixfeat: Feature or Enhancementdocs: Documentationrefactor: Refactoringchore: Build, Dependencies, Workflows, etc.other: Other (Please describe.)Breaking Changes?
Tests
Output:
Documentation
Issue References
Release Note
Additional Information