docs: add GitHub issue templates, PR template, and config

This commit is contained in:
Brad Groux 2026-01-29 00:53:43 -06:00
parent de388dc377
commit 14e69b9204
4 changed files with 100 additions and 0 deletions

41
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View file

@ -0,0 +1,41 @@
---
name: Bug Report
about: Report a bug to help us improve
title: '[BUG] '
labels: bug
assignees: ''
---
## Description
A clear and concise description of what the bug is.
## Steps to Reproduce
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
## Expected Behavior
A clear and concise description of what you expected to happen.
## Actual Behavior
A clear and concise description of what actually happened.
## Screenshots
If applicable, add screenshots to help explain your problem.
## Environment
- **OS:** [e.g., macOS 14.1, Windows 11, Ubuntu 22.04]
- **Node.js version:** [e.g., 18.17.0]
- **Browser:** [e.g., Chrome 120, Safari 17]
- **Veritas Kanban version:** [e.g., 1.0.0]
## Additional Context
Add any other context about the problem here.

5
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View file

@ -0,0 +1,5 @@
blank_issues_enabled: true
contact_links:
- name: Discussions
url: https://github.com/dm-bradgroux/veritas-kanban/discussions
about: Ask questions and share ideas

View file

@ -0,0 +1,23 @@
---
name: Feature Request
about: Suggest a new feature or enhancement
title: '[FEATURE] '
labels: enhancement
assignees: ''
---
## Problem
A clear and concise description of the problem you're trying to solve. Ex. I'm always frustrated when [...]
## Proposed Solution
A clear and concise description of what you want to happen.
## Alternatives Considered
A clear and concise description of any alternative solutions or features you've considered.
## Additional Context
Add any other context, screenshots, or examples about the feature request here.

31
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View file

@ -0,0 +1,31 @@
## Description
A clear and concise description of what this PR does.
## Type of Change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation update
- [ ] Code refactor
## Testing
**How has this been tested?**
Describe the tests you ran to verify your changes. Provide instructions so reviewers can reproduce.
**Test commands:**
```bash
# Add test commands here
```
## Checklist
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings
- [ ] Any breaking changes have been documented in the PR description