Add config.yml with blank_issues_enabled: false to all three CoP repos #174

Overview

We need to add .github/ISSUE_TEMPLATE/config.yml with blank_issues_enabled: false to all three DevOps CoP repos — devops, devops-security, and incubator — because none of them has one today, so GitHub still offers "Open a blank issue" underneath the template picker in every repo. An issue opened that way skips the forms entirely: no size/role/feature/complexity/milestone labels and no automatic add to CoP: DevOps: Project Board. Doing this in only one repo just moves the bypass to the other two, so all three are in scope for one person in one pass.

Action Items

• In hackforla/devops (default branch master), create .github/ISSUE_TEMPLATE/config.yml containing exactly:

  blank_issues_enabled: false

• Do the same in hackforla/devops-security (branch main).
• Do the same in hackforla/incubator (branch main).
• Three small PRs, one per repo — a repo cannot be changed from another repo's PR.
• After each PR merges, verify that repo: visit https://github.com/hackforla/<repo>/issues/new/choose and confirm the "Don't see your issue here? Open a blank issue." line at the bottom of the picker is gone, and that the existing templates still all appear. This step cannot be done from a PR branch — GitHub reads config.yml from the default branch only, so the change is invisible until it merges. Three separate checks, one per repo; don't close this issue until all three are done.

Resources/Instructions

• GitHub docs for this file, including the exact key name: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
• The file must be named config.yml and sit in .github/ISSUE_TEMPLATE/ alongside the templates. config.yaml is not recognised.
• This is a deliberate policy change, not just tidying: after it lands, everyone opening an issue in these repos must pick a template. That is the intent — it is what makes the labels and the board wiring on the forms actually reliable.
• Related, and part of why this matters: the DevOps CoP's Weekly Label check (Perform Weekly Label check #23) has a step for finding issues that are not on the project board. All three repos' issue forms now add new issues to board 73 automatically, so the blank-issue escape hatch is the only remaining way for an issue to arrive off-board.
• Optional and not required for this issue: config.yml can also carry a contact_links: list. Leave it out unless the CoP asks for one — the goal here is only to close the blank-issue path.