Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions .github/ISSUE_TEMPLATE/bug-report.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: Bug report
description: Report a plugin that misbehaves or gives inaccurate guidance
description: Report a problem you encountered with a plugin or with Claude's guidance
title: "[BUG]: "
labels: ["bug"]
body:
Expand All @@ -17,9 +17,7 @@ body:
- badge-progress
- workflow-guard
- Marketplace or installation
- Not sure
validations:
required: true
- Other
- type: textarea
id: problem
attributes:
Expand Down
4 changes: 0 additions & 4 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1 @@
blank_issues_enabled: true
contact_links:
- name: Report a security vulnerability
url: https://github.com/reponomics/plugins/security/policy
about: Please report vulnerabilities privately, as described in the security policy, not in a public issue.
6 changes: 3 additions & 3 deletions .github/ISSUE_TEMPLATE/suggestion.yml
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
name: Suggestion
description: Propose an improvement or support for another platform
description: Propose an improvement, feature request, or additional support for another source forge
title: "[FEAT]: "
labels: ["enhancement"]
body:
- type: textarea
id: need
attributes:
label: What benefit would this bring?
description: Describe the task or difficulty that motivates your suggestion and who it would help. If you host projects outside GitHub, tell us which forge and what the plugins currently get wrong or leave out for it.
label: What enhancement or additional functionality would you like to see?
description: Describe the task or difficulty that motivates your suggestion and who it would help. If you host projects outside GitHub, tell us which forge and what the plugins currently get wrong or how they could be improved.
validations:
required: true
- type: textarea
Expand Down
9 changes: 9 additions & 0 deletions docs/release-notes/starter-buddy/0.3.0-beta.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Starter Buddy 0.3.0-beta.2

Adjusts the bundled issue forms so new issues arrive pre-labelled and the security notice appears only where it is relevant.

- The bug, suggestion, and documentation forms now set a title prefix (`[BUG]: `, `[FEAT]: `, `[DOCS]: `) and one of GitHub's default labels (`bug`, `enhancement`, `documentation`). Starter Buddy checks that each label exists in the target repository and removes the entry or asks before creating the label.
- The instruction not to publish vulnerability details, with its link to the private reporting route, now appears only in the bug-report forms and the general report template. The suggestion and documentation forms no longer carry it.
- The chooser configuration no longer needs a security contact link: when a repository has a security policy, GitHub's issue chooser already links to it.

Forms generated with beta.1 keep working. To adopt the new defaults, add the `title` and `labels` keys to existing forms and confirm the labels exist.
6 changes: 3 additions & 3 deletions plugins/starter-buddy/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
{
"name": "starter-buddy",
"version": "0.3.0-beta.1",
"description": "Quick community-file setup for GitHub repositories: a few practical decisions, useful defaults, and optional pull request delivery",
"version": "0.3.0-beta.2",
"description": "Quick community-file setup for GitHub repositories, with practical defaults and useful templates that adjust to your needs",
"author": {
"name": "Reponomics",
"url": "https://github.com/reponomics"
"url": "https://reponomics.org"
},
"homepage": "https://github.com/reponomics/plugins/",
"repository": "https://github.com/reponomics/plugins",
Expand Down
2 changes: 1 addition & 1 deletion plugins/starter-buddy/skills/community-health/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Use `references/template-selection.md` for bundled options and `references/templ

- **README:** Start with the project purpose and verified getting-started information. Expand or curate it according to the user's interest.
- **CONTRIBUTING:** Describe accepted contributions and the project's actual setup, checks, and contribution process.
- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields and routing to the project's needs. Direct vulnerability details to a private channel.
- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields, labels, and routing to the project's needs. Direct vulnerability details to a private channel through the bug forms.
- **PR template:** Start with the short variant and add detail where useful.
- **License and conduct:** Fetch the selected canonical text and preserve its required notices. Resolve an existing licensing conflict before replacing text.
- **SECURITY:** State the confirmed support scope and a working private route. If GitHub enablement is pending, keep that dependency clear before publication.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
name: Documentation correction
description: Help us improve an explanation or resource
title: "[DOCS]: "
labels: ["documentation"]
body:
- type: markdown
attributes:
value: "Do not publish vulnerability details in this issue. Use [the private reporting instructions]({{SECURITY_POLICY_URL}})."
- type: input
id: location
attributes:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
name: Bug report
description: Explain the behavior you encountered
title: "[BUG]: "
labels: ["bug"]
body:
- type: markdown
attributes:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
name: Suggestion
description: Propose a useful improvement
title: "[FEAT]: "
labels: ["enhancement"]
body:
- type: markdown
attributes:
value: "Do not publish vulnerability details in this issue. Use [the private reporting instructions]({{SECURITY_POLICY_URL}})."
- type: textarea
id: need
attributes:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
name: Technical bug report
description: Share a reproduction and the setup where it occurs
title: "[BUG]: "
labels: ["bug"]
body:
- type: markdown
attributes:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,4 @@ Choose one default PR template and normally one primary bug-report route. Keep b

Copy and adapt the selected variants using the CC0 terms described in SKILL.md. Existing or separately sourced material retains its own licensing terms.

Replace every `{{...}}` token with confirmed information. Public issue templates use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove that link and its reference while retaining the instruction not to publish vulnerability details. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md).
Replace every `{{...}}` token with confirmed information. The bug-report forms and the general report template use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove the link from the forms while keeping the instruction not to publish vulnerability details. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md).
Original file line number Diff line number Diff line change
Expand Up @@ -33,17 +33,18 @@ Reflect established contribution requirements, such as sign-off or changelog ent

## Issue-form baseline

Keep forms brief and actionable. The bundled forms start without labels, types, projects, or assignees. Add routing details when useful and supported by the project.
Keep forms brief and actionable. The bundled forms set a title prefix (`[BUG]: `, `[FEAT]: `, `[DOCS]: `) and one of GitHub's default labels (`bug`, `enhancement`, `documentation`). Check that each label exists in the target repository; if it does not, remove the `labels` entry or create the label with the maintainer's agreement. Adjust or drop the prefixes to suit the project. The forms set no issue types, projects, or assignees; add those when useful and supported by the project.

For every YAML issue form:

- keep top-level `name`, `description`, and `body`;
- use unique, kebab-case input `id` values;
- collect the problem and reproduction information actually needed;
- explain that vulnerability details belong in the repository's confidential security route;
- avoid required fields that a reporter may not know; and
- keep the file on the default branch under `.github/ISSUE_TEMPLATE/`.

Bug-report forms and the general report template tell reporters not to publish vulnerability details and link the confidential route. Other forms omit that notice. When the repository has a security policy, GitHub's issue chooser links to it automatically, so `contact_links` does not need a security entry.

Keep blank issues enabled by default. Explain that disabling them makes templates or contact links the available entry points, and follow the maintainer’s preference. Use confirmed public URLs for `contact_links`.

The checklist does not require chooser configuration: a valid Markdown issue template or YAML issue form in `.github/ISSUE_TEMPLATE/` is enough according to GitHub's current documentation. Starter Buddy nevertheless includes `.github/ISSUE_TEMPLATE/config.yml` in its default starter pack so the blank-issue policy is visible and intentional. Use the documented filename `config.yml`.
Expand Down
Loading
Loading