chore: add GitHub issue forms and contact links - #29
Merged
Conversation
The repo is public with issues enabled and no templates, so bug reports arrive without a version, a reproducible command, or an exit code, and support questions about accounts and provisioning land here instead of with support. Three YAML forms make the required fields required. The bug form asks for account type because Build accounts are voice-only and fail messaging, number ordering, 10DLC, and toll-free commands with exit code 4 by design — that's the most likely false bug report. The command-request form encodes the rule CONTRIBUTING already states: discuss a new command before writing it. config.yml disables blank issues and points account, billing, outage, and vulnerability traffic at support, dev docs, the status page, and the bug bounty program.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
achandras
approved these changes
Aug 14, 2026
ckoegel
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The repo is public with issues enabled and no templates. Bug reports arrive without a version, a reproducible command, or an exit code — and account, billing, and provisioning questions land in this queue instead of with support.
What
Three YAML issue forms plus a config, all reusing labels that already exist on the repo (
bug,enhancement,documentation) — nothing new to create.bug_report.ymlbugband version, exact command, expected vs. actual with exit code. Dropdowns for command group (all 19 registered groups), install method, OS, account type. Opens with a redaction warning and routes vulnerabilities to SECURITY.md.command_request.ymlenhancement--wait,--if-not-exists,--plain).docs_issue.ymldocumentationconfig.ymlblank_issues_enabled: false; contact links to Bandwidth support, dev.bandwidth.com, status.bandwidth.com, and the bug bounty program.The bug form asks for account type because Build accounts are voice-only — messaging, number ordering, 10DLC, and toll-free commands fail with exit code 4 by design. That's the most likely false bug report, and knowing it up front saves a round trip.
Notes for review
/issues/newpage.[bug]-style title prefixes (labels carry that), and blank issues are off — which does mean maintainers must pick a form to file a quick note.