Skip to content

📖 Offer private vulnerability reporting in the issue chooser - #413

Open
MrBeldum wants to merge 1 commit into
ionos-cloud:mainfrom
MrBeldum:docs/issue-chooser-security-link
Open

MrBeldum wants to merge 1 commit into
ionos-cloud:mainfrom
MrBeldum:docs/issue-chooser-security-link

Conversation

@MrBeldum

@MrBeldum MrBeldum commented Oct 5, 2026

Copy link
Copy Markdown

What is the purpose of this pull request/Why do we need it?

SECURITY.md asks reporters to open a draft security advisory and not to disclose issues publicly. But there is no .github/ISSUE_TEMPLATE/config.yml, so the issue chooser only shows the public Bug report, Feature request and Release templates. A reporter has to find SECURITY.md on their own.

Issue #, if available:

None.

Description of changes:

  • Add .github/ISSUE_TEMPLATE/config.yml with a "Report a security vulnerability" contact link pointing to https://github.com/ionos-cloud/cluster-api-provider-ionoscloud/security/advisories/new, so the private route shows up in the chooser next to the public templates.
  • Keep blank_issues_enabled: true so the current behaviour doesn't change. The file only adds a route.

Special notes for your reviewer:

Private vulnerability reporting is already enabled for this repository (GET /repos/ionos-cloud/cluster-api-provider-ionoscloud/private-vulnerability-reporting returns {"enabled":true}), so the link opens the advisory form. GitHub config only. No Go code changed.

Checklist:

  • Documentation updated
  • Unit Tests added (n/a: GitHub config only)
  • E2E Tests added (n/a: GitHub config only)
  • Includes emojis

SECURITY.md points reporters at the private advisory form, but there was no
.github/ISSUE_TEMPLATE/config.yml, so the issue chooser showed only public
templates. Add a contact link to the enabled private vulnerability reporting
form so the private route is visible where a reporter decides how to file.
@sonarqubecloud

sonarqubecloud Bot commented Oct 5, 2026

Copy link
Copy Markdown

This branch had an error being deployed

1 failed deployment
e2e — af80c3ed Deployed Oct 5, 2026 by MrBeldum via e2e #694
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