chore: update github templates

This commit is contained in:
Darkraise
2026-02-03 23:41:31 +07:00
parent 8af54de927
commit 17f0cd93a7
10 changed files with 132 additions and 334 deletions
-75
View File
@@ -1,75 +0,0 @@
---
name: Bug Report
about: Report a bug or unexpected behavior
title: '[BUG] '
labels: bug, triage
assignees: ''
---
## Bug 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
**Desktop:**
- OS: [e.g., Windows 11, macOS 14, Ubuntu 22.04]
- Browser: [e.g., Chrome 120, Firefox 121, Safari 17]
- Node.js version: [e.g., 20.11.0]
**Flashpoint Web Version:**
- Backend version: [e.g., commit hash or version]
- Frontend version: [e.g., commit hash or version]
**Flashpoint Archive:**
- Flashpoint version: [e.g., Flashpoint 12]
- Installation type: [e.g., Infinity, Ultimate]
## Logs
<!-- If applicable, paste relevant error logs here. -->
<details>
<summary>Backend Logs</summary>
```
Paste backend logs here
```
</details>
<details>
<summary>Browser Console</summary>
```
Paste browser console errors here
```
</details>
## Additional Context
<!-- Add any other context about the problem here. -->
## Possible Solution
<!-- If you have ideas on how to fix this, please share. -->
+71
View File
@@ -0,0 +1,71 @@
name: Bug Report
description: Report a bug or unexpected behavior
title: "[Bug] "
labels: ["bug"]
body:
- type: textarea
id: description
attributes:
label: What happened?
description: A clear description of the bug.
placeholder: "When I click X, Y happens instead of Z..."
validations:
required: true
- type: textarea
id: steps
attributes:
label: Steps to reproduce
description: How can we reproduce this?
placeholder: |
1. Go to '...'
2. Click on '...'
3. See error
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
placeholder: "I expected..."
validations:
required: false
- type: textarea
id: screenshots
attributes:
label: Screenshots / Logs
description: Paste screenshots, browser console errors, or backend logs.
validations:
required: false
- type: input
id: flashpoint-version
attributes:
label: Flashpoint version
placeholder: "e.g., Flashpoint 14.0.3 Infinity"
validations:
required: false
- type: input
id: browser
attributes:
label: Browser
placeholder: "e.g., Chrome 120, Firefox 121"
validations:
required: false
- type: dropdown
id: service
attributes:
label: Which part is affected?
options:
- Frontend (UI)
- Backend (API)
- Game Player
- Game Service
- Docker / Deployment
- Don't know
validations:
required: false
+5 -5
View File
@@ -1,10 +1,10 @@
blank_issues_enabled: false
blank_issues_enabled: true
contact_links:
- name: Documentation
url: https://github.com/YOUR_USERNAME/flashpoint-web/tree/master/docs
about: Check the documentation before opening an issue
- name: Ask a Question
url: https://github.com/darkraise/flashpoint-web/discussions
about: Use Discussions for questions, help, and general conversation
- name: Flashpoint Archive
url: https://flashpointarchive.org/
url: https://github.com/FlashpointProject
about: For issues with Flashpoint itself (not this web interface)
- name: Ruffle Flash Emulator
url: https://github.com/ruffle-rs/ruffle/issues
-56
View File
@@ -1,56 +0,0 @@
---
name: Documentation
about: Report documentation issues or suggest improvements
title: '[DOCS] '
labels: documentation
assignees: ''
---
## Documentation Issue Type
- [ ] Missing documentation
- [ ] Incorrect/outdated information
- [ ] Unclear explanation
- [ ] Typo/grammar
- [ ] Broken links
- [ ] Missing code examples
- [ ] Other: ___________
## Location
<!-- Where is the documentation issue? -->
**File path:** `docs/...`
**URL (if applicable):**
**Section/Heading:**
## Current Content
<!-- Quote or describe the current documentation. -->
```
Current text here...
```
## Problem Description
<!-- What's wrong with the current documentation? -->
## Suggested Improvement
<!-- How should it be changed? -->
```
Suggested text here...
```
## Additional Context
<!-- Any other information that might help. -->
## Checklist
- [ ] I have checked that this isn't already documented elsewhere
- [ ] I have verified the information I'm suggesting is accurate
-77
View File
@@ -1,77 +0,0 @@
---
name: Enhancement
about: Suggest an improvement to existing functionality
title: '[ENHANCEMENT] '
labels: enhancement
assignees: ''
---
## Enhancement Description
<!-- A clear and concise description of the enhancement you're proposing. -->
## Current Behavior
<!-- Describe how the feature currently works. -->
## Proposed Improvement
<!-- Describe how you'd like the feature to work instead. -->
## Benefits
<!-- Explain the benefits of this enhancement. -->
-
-
-
## Affected Area
<!-- Which part of the application does this affect? -->
- [ ] UI/UX
- [ ] Performance
- [ ] API
- [ ] Database
- [ ] Authentication
- [ ] Game Player
- [ ] Search/Filtering
- [ ] Playlists
- [ ] Admin Panel
- [ ] Other: ___________
## Affected Services
- [ ] Backend
- [ ] Frontend
- [ ] Game Service
- [ ] Documentation
## Breaking Changes
<!-- Will this enhancement require breaking changes? -->
- [ ] Yes (describe below)
- [ ] No
- [ ] Unknown
<!-- If yes, describe what would break: -->
## Implementation Suggestions
<!-- Optional: Share ideas on how to implement this. -->
## Screenshots / Mockups
<!-- If applicable, add visuals showing the proposed enhancement. -->
## Related Issues
<!-- Link any related issues or PRs. -->
- #
## Additional Context
<!-- Add any other context here. -->
-71
View File
@@ -1,71 +0,0 @@
---
name: Feature Request
about: Suggest a new feature for the project
title: '[FEATURE] '
labels: enhancement, feature-request
assignees: ''
---
## Feature Description
<!-- A clear and concise description of the feature you'd like. -->
## Problem Statement
<!-- Is this feature related to a problem? Describe it. -->
<!-- Example: "I'm frustrated when..." -->
## Proposed Solution
<!-- Describe the solution you'd like. -->
## User Story
<!-- Optional: Describe the feature from a user's perspective. -->
<!-- Example: "As a [type of user], I want [goal] so that [benefit]." -->
As a **[user type]**, I want **[goal/desire]** so that **[benefit/value]**.
## Use Cases
<!-- List specific scenarios where this feature would be useful. -->
1.
2.
3.
## Mockups / Examples
<!-- If applicable, add mockups, wireframes, or examples from other apps. -->
## Alternatives Considered
<!-- Describe any alternative solutions or features you've considered. -->
## Implementation Ideas
<!-- Optional: Share any thoughts on how this could be implemented. -->
### Affected Services
- [ ] Backend
- [ ] Frontend
- [ ] Game Service
- [ ] Documentation
### Estimated Complexity
- [ ] Small (few hours)
- [ ] Medium (1-3 days)
- [ ] Large (1+ week)
- [ ] Unknown
## Additional Context
<!-- Add any other context, screenshots, or references here. -->
## Checklist
- [ ] I have searched existing issues to ensure this isn't a duplicate
- [ ] I have provided clear use cases for this feature
- [ ] I have considered how this fits with existing functionality
@@ -0,0 +1,44 @@
name: Feature Request
description: Suggest a new feature or improvement
title: "[Feature] "
labels: ["enhancement"]
body:
- type: textarea
id: description
attributes:
label: What would you like?
description: Describe the feature or improvement.
placeholder: "It would be great if..."
validations:
required: true
- type: textarea
id: problem
attributes:
label: Why?
description: What problem does this solve, or what use case does it enable?
placeholder: "Currently I have to... / This would help with..."
validations:
required: false
- type: textarea
id: ideas
attributes:
label: Ideas / Mockups
description: Optional implementation ideas, mockups, or examples from other apps.
validations:
required: false
- type: dropdown
id: service
attributes:
label: Which part is affected?
options:
- Frontend (UI)
- Backend (API)
- Game Player
- Game Service
- Documentation
- Don't know
validations:
required: false
-38
View File
@@ -1,38 +0,0 @@
---
name: Question
about: Ask a question about the project
title: '[QUESTION] '
labels: question
assignees: ''
---
## Question
<!-- What would you like to know? -->
## Context
<!-- Provide any relevant context for your question. -->
## What I've Tried
<!-- What have you already looked at or tried? -->
- [ ] Read the documentation at `docs/`
- [ ] Searched existing issues
- [ ] Checked the README
- [ ] Other: ___________
## Related Documentation
<!-- Link any docs you've already reviewed. -->
## Environment (if relevant)
- OS:
- Node.js version:
- Browser:
## Additional Information
<!-- Any other details that might help answer your question. -->
+10 -10
View File
@@ -45,9 +45,9 @@ The workflow pushes images to **Docker Hub**.
4. **Images will be pushed to**:
```
docker.io/<dockerhub-username>/flashpoint-backend:latest
docker.io/<dockerhub-username>/flashpoint-frontend:latest
docker.io/<dockerhub-username>/flashpoint-game-service:latest
docker.io/darkraise/flashpoint-backend:latest
docker.io/darkraise/flashpoint-frontend:latest
docker.io/darkraise/flashpoint-game-service:latest
```
#### Image Tags
@@ -102,12 +102,12 @@ The workflow uses GitHub Actions cache to speed up builds:
```bash
# Pull latest images
docker pull <dockerhub-username>/flashpoint-backend:latest
docker pull <dockerhub-username>/flashpoint-frontend:latest
docker pull <dockerhub-username>/flashpoint-game-service:latest
docker pull darkraise/flashpoint-backend:latest
docker pull darkraise/flashpoint-frontend:latest
docker pull darkraise/flashpoint-game-service:latest
# Or use a specific version
docker pull <dockerhub-username>/flashpoint-backend:1.0.0
docker pull darkraise/flashpoint-backend:1.0.0
```
##### Use in Docker Compose
@@ -119,20 +119,20 @@ version: '3.8'
services:
backend:
image: <dockerhub-username>/flashpoint-backend:latest
image: darkraise/flashpoint-backend:latest
# Remove build section
ports:
- "3100:3100"
# ... rest of config
frontend:
image: <dockerhub-username>/flashpoint-frontend:latest
image: darkraise/flashpoint-frontend:latest
ports:
- "80:8080"
# ... rest of config
game-service:
image: <dockerhub-username>/flashpoint-game-service:latest
image: darkraise/flashpoint-game-service:latest
ports:
- "22500:22500"
- "22501:22501"
+2 -2
View File
@@ -71,8 +71,8 @@ jobs:
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
cache-from: type=gha
cache-to: type=gha,mode=max
cache-from: type=gha,scope=${{ matrix.service.name }}
cache-to: type=gha,scope=${{ matrix.service.name }},mode=max
platforms: linux/amd64
build-args: |
BUILD_DATE=${{ fromJSON(steps.meta.outputs.json).labels['org.opencontainers.image.created'] }}