chore: add issue templates (bug report + feature request) - #13
Merged
Merged
Conversation
Add GitHub issue forms so external reports arrive structured and share-safe now that the repo is public: - bug_report.yml: required what-happened / repro / area / environment, optional version and shell-rendered logs, dupe + not-a-vuln checks. - feature_request.yml: problem, proposal, area, alternatives. - config.yml: keep blank issues on; route security reports to SECURITY.md and setup questions to the deployment docs. Both forms warn against pasting tokens, admins.yaml, IDs, or gateway credentials, and point security issues to the private policy. Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
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
1 participant
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.
What
Adds GitHub issue forms now that the repo is public, so incoming reports arrive structured and share-safe.
bug_report.yml— required what happened, steps to reproduce, area, and environment; optional version/commit and shell-rendered logs; "searched issues" and "not a security vuln" checkboxes.feature_request.yml— problem/use case, proposed solution, area, alternatives considered.config.yml— keeps blank issues enabled; routes security reports toSECURITY.mdand setup/deployment questions todocs/03-deployment.mdvia contact links.Why
Public repo, issues enabled. Templates guide reporters toward reproducible bugs and steer sensitive reports to the right channel.
Safety
Both forms explicitly warn against pasting Slack tokens,
config/admins.yamlcontents, channel/user IDs, or gateway credentials, and point security vulnerabilities to the private policy instead of a public issue. The bug form nudges reporters toward the share-safenpm run support-bundle.Notes
yamlparser (both forms + config parse; field counts 8 / 6 / 2 contact links).Co-Authored-By: Claude svc-devxp-claude@slack-corp.com