docs: add SECURITY.md and GitHub issue templates
Add a security policy directing private vulnerability reports to security@astrolabecloud.com instead of public issues, and update the README's Security section to point at it. Add structured issue forms under .github/ISSUE_TEMPLATE/ covering bugs, feature requests, questions, and documentation, plus a config.yml that disables blank issues and routes security reports and open-ended questions to the appropriate channels. The bug template captures fields most commonly missing from past reports (server/Nextcloud/app versions, deployment mode, transport, MCP client). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.7
parent
a9c5759869
commit
8cc84ac08b
@@ -0,0 +1,8 @@
|
||||
blank_issues_enabled: false
|
||||
contact_links:
|
||||
- name: Security vulnerability
|
||||
url: https://github.com/cbcoutinho/nextcloud-mcp-server/blob/master/SECURITY.md
|
||||
about: Do not file security issues publicly. Email security@astrolabecloud.com — see SECURITY.md.
|
||||
- name: Question or discussion
|
||||
url: https://github.com/cbcoutinho/nextcloud-mcp-server/discussions
|
||||
about: For general questions, deployment help, or open-ended discussion, please use Discussions instead of opening an issue.
|
||||
Reference in New Issue
Block a user