starred/f1-race-replay
1
0
Fork 0
mirror of https://github.com/IAmTomShaw/f1-race-replay.git synced 2026-05-09 08:25:56 +02:00
Code Issues 133 Projects Packages Wiki Activity

[PR #122] Add GitHub issue and PR templates for better project organization #154

New issue
Open
opened 2026-05-07 00:18:57 +02:00 by BreizhHardware · 0 comments
BreizhHardware commented 2026-05-07 00:18:57 +02:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/IAmTomShaw/f1-race-replay/pull/122
Author: @josiah-mbao
Created: 12/24/2025
Status: 🔄 Open

Base: main ← Head: add-github-templates

📝 Commits (1)

  • c84b724 Add GitHub issue and PR templates for better project organization

📊 Changes

3 files changed (+103 additions, -0 deletions)

View changed files

➕ .github/ISSUE_TEMPLATE/bug_report.md (+37 -0)
➕ .github/ISSUE_TEMPLATE/feature_request.md (+28 -0)
➕ .github/PULL_REQUEST_TEMPLATE.md (+38 -0)

📄 Description

I have successfully completed the implementation of GitHub issue and PR templates, addressing Issue #119. Here's what was accomplished:

✅ Completed Tasks:

  1. Created GitHub Issue Templates:

    • bug_report.md - Structured template for reporting bugs with environment info, reproduction steps, and expected behavior
    • feature_request.md - Template for suggesting new features with problem description and solution details

  2. Created Pull Request Template:

    • PULL_REQUEST_TEMPLATE.md - Comprehensive checklist including summary, test plan, documentation, and code quality guidelines

  3. Successfully Implemented:

    • Created .github/ISSUE_TEMPLATE/ directory structure
    • Added all three template files with proper YAML frontmatter
    • Created new branch add-github-templates
    • Committed changes with message: "Add GitHub issue and PR templates for better project organization"
    • Pushed branch to remote repository

🎯 Benefits of This Contribution:

  • Prevents spam/unwanted issues - Structured templates guide users to provide relevant information
  • Uniform format - All issues and PRs will follow the same structure
  • Better project organization - Easier for maintainers to triage and respond
  • Improved contributor experience - Clear guidelines for submitting issues and PRs
  • Directly addresses Issue #119 - Solves the exact problem requested by @viralcodex

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/IAmTomShaw/f1-race-replay/pull/122 **Author:** [@josiah-mbao](https://github.com/josiah-mbao) **Created:** 12/24/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-github-templates` --- ### 📝 Commits (1) - [`c84b724`](https://github.com/IAmTomShaw/f1-race-replay/commit/c84b72435943059d9b88c849b1c11fda7d12dd04) Add GitHub issue and PR templates for better project organization ### 📊 Changes **3 files changed** (+103 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/ISSUE_TEMPLATE/bug_report.md` (+37 -0) ➕ `.github/ISSUE_TEMPLATE/feature_request.md` (+28 -0) ➕ `.github/PULL_REQUEST_TEMPLATE.md` (+38 -0) </details> ### 📄 Description I have successfully completed the implementation of GitHub issue and PR templates, addressing Issue #119. Here's what was accomplished: ## ✅ __Completed Tasks:__ 1. __Created GitHub Issue Templates:__ - `bug_report.md` - Structured template for reporting bugs with environment info, reproduction steps, and expected behavior - `feature_request.md` - Template for suggesting new features with problem description and solution details 2. __Created Pull Request Template:__ - `PULL_REQUEST_TEMPLATE.md` - Comprehensive checklist including summary, test plan, documentation, and code quality guidelines 3. __Successfully Implemented:__ - Created `.github/ISSUE_TEMPLATE/` directory structure - Added all three template files with proper YAML frontmatter - Created new branch `add-github-templates` - Committed changes with message: "Add GitHub issue and PR templates for better project organization" - Pushed branch to remote repository ## 🎯 __Benefits of This Contribution:__ - __Prevents spam/unwanted issues__ - Structured templates guide users to provide relevant information - __Uniform format__ - All issues and PRs will follow the same structure - __Better project organization__ - Easier for maintainers to triage and respond - __Improved contributor experience__ - Clear guidelines for submitting issues and PRs - __Directly addresses Issue #119__ - Solves the exact problem requested by @viralcodex --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dial-insight
driver-telemetry-pit-wall-window
pit-wall-telemetry-windows
telemetry-stream
organised-legend
158-race-replay-leaderboard-inaccurate
No results found.
Labels
Clear labels   
bug

   
enhancement

   
pull-request
Mirrored from GitHub Pull Request

No labels
bug
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/f1-race-replay#154
No description provided.