genval-github-integration[bot]
commented
14 hours ago Pre Refactor Summary
| Property | Value |
|---|---|
| Proposed Branch Name | feature/generate-github-issue-templates |
| Total Files in Scope | 11 |
| Estimated Input Tokens | 10048 |
Details
Scope Patterns
```text .genval/definitions/tasks/*.md .github/ISSUE_TEMPLATE/* ```
Files in Scope
| File | Estimated Tokens | |------|------------------| | .github/ISSUE_TEMPLATE/build-stack-definitions.yaml | 1389 | | .genval/definitions/tasks/build-stack-definitions.md | 1137 | | .github/ISSUE_TEMPLATE/build-models-from-definitions.yaml | 912 | | .github/ISSUE_TEMPLATE/convert-from-sqlserver-to-postgress.yaml | 822 | | .github/ISSUE_TEMPLATE/generate-issue-templates-from-task-definitions.yaml | 725 | | .genval/definitions/tasks/build-models-from-definitions.md | 699 | | .genval/definitions/tasks/generate-issue-templates-from-task-definitions.md | 632 | | .genval/definitions/tasks/models-to-code.md | 613 | | .genval/definitions/tasks/convert-from-sqlserver-to-postgress.md | 507 | | .github/ISSUE_TEMPLATE/refactor.yaml | 331 | | .genval/definitions/tasks/refactor.md | 302 |
Processing Instructions
Look at each markdown file found in the
.genval/definitions/tasksdirectory. Each file will be used to generate a Github Issue Template in YAML which we'll name like this:.github/ISSUE_TEMPLATE/{task-code}.yamlwhere{task-code}is a unique code of the task definition markdown file you are processing (without the .md extension).Use your best judgement about how to create a Github Issue Form user input elements that is user friendly and helpful for items described in the
### User Inputsection of the task definition file. This is where you can break up the description into individual input elements. Be sure to set default values, if you think there should be default values. Use thevalueattribute to set a default value, notdefault.For the
### Processing Instructionssection you can just create a single textarea input box with the instructions formatted as markdown. Be sure to use textarea (not markdown) as the element type, because we need the value to come through when the user submits the issue. Markdown element types don't actually come through to the issue body when you create an issue, so we have to use the textarea element type.Title: Use the following pattern when generating the title:
{task-title}where{task-title}is the a title for the type of task you are working with.If the definition file includes
### Scope Patternsyou can just include those as they are written.Note: When adding Markdown you are required to specify a
valueattribute, but you can not specify alabelattribute. So any markdown text should be set in thevalueattribute.Scope Patterns
Source Branch
main