Skip to content

fix(issue-template): replace role dropdown with affected component input - #83

Merged
sbaerlocher merged 1 commit into
mainfrom
fix/issue-templates-neutral
Aug 8, 2026
Merged

fix(issue-template): replace role dropdown with affected component input#83
sbaerlocher merged 1 commit into
mainfrom
fix/issue-templates-neutral

Conversation

@sbaerlocher

Copy link
Copy Markdown
Member

Summary

  • The required role dropdown (Alloy, DO, Tailscale) in all three issue templates came from ansible.agent and is meaningless in every other repository these org-wide defaults apply to — go.ansible and guide have no roles at all, yet every reporter there had to pick one. It is now an optional free-form Affected Component(s) input, matching what pull_request_template.md already received in fix(pr-template): generalize org-wide PR template #68.
  • The bug report asked for the version of arillso.agent specifically; it now asks for the version of the affected component. The arillso.agent playbook examples are replaced by neutral placeholders.
  • Root and templates/ copies stay byte-identical, so repositories bootstrapped from the templates get the same forms.

Test plan

  • All six templates parse as YAML and satisfy the issue-forms schema (block types, unique ids, dropdowns carry options) — verified locally
  • diff confirms each root template is byte-identical to its templates/ counterpart — verified locally
  • No arillso.agent, Alloy, DO or Tailscale references remain in either template directory — verified by repo-wide grep
  • CI green

The required role dropdown (Alloy, DO, Tailscale) came from ansible.agent and
is meaningless in every other repository these org-wide defaults apply to, so
reporters in repositories without roles had to pick one anyway. It is now an
optional free-form Affected Component(s) input, matching the PR template.

Signed-off-by: Simon Bärlocher <s.baerlocher@sbaerlocher.ch>
label: Collection Version
description: What version of arillso.agent are you using?
label: Version
description: What version of the affected component are you using?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking follow-up: this PR generalizes the templates for all repo types and correctly makes Version neutral, but two fields just below remain Ansible-specific and required, which reintroduces the exact problem this PR fixes for the role dropdown:

  • Ansible Version (id: ansible-version, required: true) — meaningless in go.ansible/guide and Go/Actions repos, yet mandatory to submit.
  • The checklist item I am using a supported platform and Ansible version (required: true).
  • The Operating System dropdown also lists only Linux distros.

Per the PR's own rationale ("meaningless in every other repository these org-wide defaults apply to"), consider making these optional / neutral too (here and in the identical templates/ISSUE_TEMPLATE/bug_report.yml). Fine as a separate change if you'd rather keep this PR narrowly scoped.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blocking issues found. The change cleanly replaces the required, ansible.agent-specific role dropdown with an optional free-form Affected Component(s) input across all three issue templates, neutralizes the playbook examples, and keeps the root and templates/ copies byte-identical (verified). CHANGELOG entry is in the correct Changed section.

One non-blocking follow-up left inline: bug_report.yml still keeps a required Ansible Version field and an Ansible-specific checklist item, which are meaningless in the non-Ansible repos these org-wide defaults also apply to — the same class of problem this PR fixes for the role dropdown. Fine to address separately if you'd rather keep this PR narrowly scoped.

@sbaerlocher
sbaerlocher merged commit dd59b03 into main Aug 8, 2026
7 checks passed
@sbaerlocher
sbaerlocher deleted the fix/issue-templates-neutral branch August 8, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant