Skip to content

Security policy and issue templates, as in Parallels Manager - #12

Merged
kellylford merged 1 commit into
mainfrom
security-and-issue-templates
Oct 16, 2026
Merged

kellylford merged 1 commit into
mainfrom
security-and-issue-templates

Conversation

@kellylford

Copy link
Copy Markdown
Contributor

Quick Describe is public now, so it gets what Parallels Manager has:

  • SECURITY.md: report privately (GitHub private vulnerability reporting, which is on, or email), and what Quick Describe captures, keeps and sends. Checked against the code: the log records what went wrong, not descriptions; releases are signed with Azure Artifact Signing (no checksums are published, so it doesn't claim any).
  • Issue templates: Report a problem (version from Help, About; Windows and Copilot+ PC; screen reader; log) and Suggest an idea, using the repo's existing bug and enhancement labels, plus a link to private security reporting. Blank issues stay on, so Report a Bug's fallback link, /issues/new?title=…&body=…, still opens a filled-in issue.

Settings changed outside this PR: the azure-signing environment now allows only v* tags (release.yml's comment already said it did, but no policy was set), and the repo has topics and a homepage link.

🤖 Generated with Claude Code

SECURITY.md says how to report a security problem privately and what Quick Describe captures,
keeps and sends. The issue templates ask for the version, Windows, the screen reader and the log,
and point security problems at private reporting.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kellylford
kellylford merged commit 646ff5e into main Oct 16, 2026
4 checks passed
@kellylford
kellylford deleted the security-and-issue-templates branch October 16, 2026 20:06
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