starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

[PR #802] [MERGED] Github: Optimize Issue Template & PR Template #2750

New Issue
Closed
opened 2026-02-05 05:11:17 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 05:11:17 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/802
Author: @MickLesk
Created: 12/13/2024
Status: ✅ Merged
Merged: 12/13/2024
Merged by: @MickLesk

Base: main ← Head: optimize_bug_reports

📝 Commits (5)

���� Changes

2 files changed (+77 additions, -40 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE/bug_report.yml (+49 -20)
📝 .github/pull_request_template.md (+28 -20)

📄 Description

Description

  • Optimize Issue Template
  • Add 2 new Fields: Source & Source-URL (because 25% of the bugs are from the tteck repo and the constant inquiring and waiting is annoying.
  • Little bit better UI
  • Add Ubuntu 24.10 for PR (It could also be done later, but it just makes another pointless 1-line PR that has to be checked)

  • Optimize PR Template
  • Slightly shifted the values and more sensible order
  • Little bit better UI

Provide a summary of the changes made and/or reference the issue being addressed.

Fixes # (issue)

Type of change

Please check the relevant option(s):

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
  • New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites

The following efforts must be made for the PR to be considered. Please check when completed:

  • Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
  • Testing performed (I have tested my changes, ensuring everything works as expected)
  • Documentation updated (I have updated any relevant documentation)

Additional Information (optional)

Provide any additional context or screenshots about the feature or fix here.

image

🔄 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/community-scripts/ProxmoxVE/pull/802 **Author:** [@MickLesk](https://github.com/MickLesk) **Created:** 12/13/2024 **Status:** ✅ Merged **Merged:** 12/13/2024 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `optimize_bug_reports` --- ### 📝 Commits (5) - [`4fabd88`](https://github.com/community-scripts/ProxmoxVE/commit/4fabd88531887d103f44c2dcd93b3a9e6f91ea8b) Update bug_report.yml - [`0cf0c63`](https://github.com/community-scripts/ProxmoxVE/commit/0cf0c630570e055bca2d2803b6b09c872c43a0b7) Update bug_report.yml - [`4e4495f`](https://github.com/community-scripts/ProxmoxVE/commit/4e4495f150a4ca15f4a7b36f76de633c5e1ee136) Update bug_report.yml - [`def5253`](https://github.com/community-scripts/ProxmoxVE/commit/def5253ebc786c1c7e83c89a323255d90558b823) Update bug_report.yml - [`c694bc9`](https://github.com/community-scripts/ProxmoxVE/commit/c694bc9055159a26ad5308e3899321fed269e258) Update pull_request_template.md ### ���� Changes **2 files changed** (+77 additions, -40 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE/bug_report.yml` (+49 -20) 📝 `.github/pull_request_template.md` (+28 -20) </details> ### 📄 Description ## Description - Optimize Issue Template - Add 2 new Fields: Source & Source-URL (because 25% of the bugs are from the tteck repo and the constant inquiring and waiting is annoying. - Little bit better UI - Add Ubuntu 24.10 for PR (It could also be done later, but it just makes another pointless 1-line PR that has to be checked) </br> - Optimize PR Template - Slightly shifted the values and more sensible order - Little bit better UI Provide a summary of the changes made and/or reference the issue being addressed. Fixes # (issue) ## Type of change Please check the relevant option(s): - [ ] Bug fix (non-breaking change that resolves an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly) - [ ] New script (a fully functional and thoroughly tested script or set of scripts.) ## Prerequisites The following efforts must be made for the PR to be considered. Please check when completed: - [x] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions) - [x] Testing performed (I have tested my changes, ensuring everything works as expected) - [x] Documentation updated (I have updated any relevant documentation) ## Additional Information (optional) Provide any additional context or screenshots about the feature or fix here. ![image](https://github.com/user-attachments/assets/20ceb636-e17c-41b8-b880-847280b828b3) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 05:11:17 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2750
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?