Closed paulfryer closed 17 hours ago
Property | Value |
---|---|
Proposed Branch Name | feature/issue-template-generator |
Total Files in Scope | 2 |
Estimated Input Tokens | 2654 |
```text .genval/definitions/tasks/*.md ```
| File | Estimated Tokens | |------|------------------| | .genval/definitions/tasks/generate-issue-templates-from-task-definitions.md | 561 | | .genval/definitions/tasks/refactor.md | 300 |
File Name | Action | Summary of Changes |
---|---|---|
.github/ISSUE_TEMPLATE/generate-issue-templates-from-task-definitions.yaml | CREATE | Created a new GitHub Issue Template for generating issue templates from task definitions |
.github/ISSUE_TEMPLATE/refactor.yaml | CREATE | Created a new GitHub Issue Template for refactoring tasks |
Generate Issue Templates from Task Definitions
Processing Instructions
I want you to look at each markdown file found in the
.genval/definitions/tasks
directory. Each file will be used to generate a Github Issue Template in YAML which we'll name like this:.github/ISSUE_TEMPLATE/{task-code}.yaml
where{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 Input
section 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 thevalue
attribute to set a default value, notdefault
.For the
### Processing Instructions
section 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 Patterns
you can just include those as they are written.Note: When adding Markdown you are required to specify a
value
attribute, but you can not specify alabel
attribute. So any markdown text should be set in thevalue
attribute.Scope Patterns
This should be presented as a textarea with this literal value:
It's important to include the opening and closing tripple asterisk along with the
text Scope Patterns
part in the textarea.