Overview
We need to fix two defects in the two blank issue forms in devops-security and incubator, so that the Dependency field's required: true can actually block an empty submission and the house-style Overview convention is visible to whoever is writing the issue. This repo already has both right; those two are what is left of the gap that #173 closed here.
This is filed on devops as a single cross-repo ticket — two small PRs, one assignee — the same way #174 was handled, because the two changes have to land together to keep the forms identical.
Action Items
The forms in the two repos are byte-identical pairs — devops-security and incubator hold the same two files, character for character (verified 2026-08-26). Make the same edit in all four files and keep them identical; the two repos should still diff clean when you are done.
Files, same names in both repos, under .github/ISSUE_TEMPLATE/:
blank-issue-form-with-dependency.yml and blank-issue-form-with-no-dependency.yml.
1. Make the Dependency field's required: true real
In blank-issue-form-with-dependency.yml (line 11 when written, may drift — find it by the value: key under id: dependency) the field is prefilled:
Why this matters rather than being cosmetic: value: writes the text into the textarea, so the field is never empty, so the required: true two lines below it can never fail. Anyone can submit the dependency form with a bare unchecked box and no blocker listed, and the rendered issue then opens with an empty checklist that reads as if it means something. placeholder: shows the same hint as grey prompt text without putting it in the submitted body, which is what makes the requirement bite. This repo's equivalent field already uses placeholder:, and #173 made exactly this change to this repo's Action Items and Resources fields.
2. Restore the house-style Overview guidance
Neither form tells the writer the CoP's Overview convention. It only ever appeared in blank-issue-template.md, which was deleted in hackforla/devops-security#162, so the convention is currently undocumented in the two templates people actually use. devops carries it as a placeholder: on the Overview field.
Copy it verbatim from this repo's .github/ISSUE_TEMPLATE/blank-issue-form.yml rather than retyping it, so all three repos end up on one wording instead of three. It goes directly under the existing description: Clearly state the purpose of this issue in 2 sentences or less line (line 18 in the dependency form, line 10 in the no-dependency form — accurate when written; find it by the label: Overview above it). Use placeholder:, not value: — the point of item 1 applies here too.
3. Verify after the PRs merge
GitHub renders issue templates from the default branch only, so none of this is observable from a branch — you have to come back after merge.
Resources/Instructions
Deliberately out of scope. Resources/Instructions is also marked required: true in these forms, which manufactures "N/A" filler on issues that genuinely have no external resource. That is not fixed here because it applies identically to all three repos, and changing it in two of them would create a new divergence rather than close one. It stays an open convergence decision.
Overview
We need to fix two defects in the two blank issue forms in
devops-securityandincubator, so that the Dependency field'srequired: truecan actually block an empty submission and the house-style Overview convention is visible to whoever is writing the issue. This repo already has both right; those two are what is left of the gap that #173 closed here.This is filed on
devopsas a single cross-repo ticket — two small PRs, one assignee — the same way #174 was handled, because the two changes have to land together to keep the forms identical.Action Items
The forms in the two repos are byte-identical pairs —
devops-securityandincubatorhold the same two files, character for character (verified 2026-08-26). Make the same edit in all four files and keep them identical; the two repos should still diff clean when you are done.Files, same names in both repos, under
.github/ISSUE_TEMPLATE/:blank-issue-form-with-dependency.ymlandblank-issue-form-with-no-dependency.yml.1. Make the Dependency field's
required: truerealIn
blank-issue-form-with-dependency.yml(line 11 when written, may drift — find it by thevalue:key underid: dependency) the field is prefilled:value:toplaceholder:inhackforla/devops-securityvalue:toplaceholder:inhackforla/incubatorWhy this matters rather than being cosmetic:
value:writes the text into the textarea, so the field is never empty, so therequired: truetwo lines below it can never fail. Anyone can submit the dependency form with a bare unchecked box and no blocker listed, and the rendered issue then opens with an empty checklist that reads as if it means something.placeholder:shows the same hint as grey prompt text without putting it in the submitted body, which is what makes the requirement bite. This repo's equivalent field already usesplaceholder:, and #173 made exactly this change to this repo's Action Items and Resources fields.2. Restore the house-style Overview guidance
Neither form tells the writer the CoP's Overview convention. It only ever appeared in
blank-issue-template.md, which was deleted in hackforla/devops-security#162, so the convention is currently undocumented in the two templates people actually use.devopscarries it as aplaceholder:on the Overview field.placeholder:block to both forms inhackforla/devops-securityplaceholder:block to both forms inhackforla/incubatorCopy it verbatim from this repo's
.github/ISSUE_TEMPLATE/blank-issue-form.ymlrather than retyping it, so all three repos end up on one wording instead of three. It goes directly under the existingdescription: Clearly state the purpose of this issue in 2 sentences or lessline (line 18 in the dependency form, line 10 in the no-dependency form — accurate when written; find it by thelabel: Overviewabove it). Useplaceholder:, notvalue:— the point of item 1 applies here too.3. Verify after the PRs merge
GitHub renders issue templates from the default branch only, so none of this is observable from a branch — you have to come back after merge.
devops-securityPR merges, open https://github.com/hackforla/devops-security/issues/new/choose, start the dependency form, and confirm the Dependency box is empty with grey placeholder text and that submitting it empty is blockedincubatorPR merges, repeat both checks at https://github.com/hackforla/incubator/issues/new/chooseResources/Instructions
value:→placeholder:fix: Blank issue forms ship 'Item 1 / Item 2' - switch prefilled value: to placeholder: #173. Prior art for a cross-repo template ticket filed here: Add config.yml with blank_issues_enabled: false to all three CoP repos #174valueprefills,placeholderdoes notDeliberately out of scope.
Resources/Instructionsis also markedrequired: truein these forms, which manufactures "N/A" filler on issues that genuinely have no external resource. That is not fixed here because it applies identically to all three repos, and changing it in two of them would create a new divergence rather than close one. It stays an open convergence decision.