fix(issue-template): replace role dropdown with affected component input - #83
Conversation
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? |
There was a problem hiding this comment.
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 ingo.ansible/guideand Go/Actions repos, yet mandatory to submit.- The checklist item
I am using a supported platform and Ansible version(required: true). - The
Operating Systemdropdown 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.
There was a problem hiding this comment.
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.
Summary
ansible.agentand is meaningless in every other repository these org-wide defaults apply to —go.ansibleandguidehave no roles at all, yet every reporter there had to pick one. It is now an optional free-formAffected Component(s)input, matching whatpull_request_template.mdalready received in fix(pr-template): generalize org-wide PR template #68.arillso.agentspecifically; it now asks for the version of the affected component. Thearillso.agentplaybook examples are replaced by neutral placeholders.templates/copies stay byte-identical, so repositories bootstrapped from the templates get the same forms.Test plan
diffconfirms each root template is byte-identical to itstemplates/counterpart — verified locallyarillso.agent, Alloy, DO or Tailscale references remain in either template directory — verified by repo-wide grep