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

[PR #1285] [MERGED] fix: buffer from base64 in formatting pipeline #2967

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

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1285
Author: @se-bastiaan
Created: 1/6/2025
Status: ✅ Merged
Merged: 1/6/2025
Merged by: @MickLesk

Base: main ← Head: fix/formatting-pipeline

📝 Commits (2)

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 .github/workflows/validate-formatting.yaml (+2 -2)

📄 Description

🛠️ Note:
We are meticulous about merging code into the main branch, so please understand that pull requests not meeting the project's standards may be rejected. It's never personal!
🎮 Note for game-related scripts: These have a lower likelihood of being merged.

✍️ Description

This pull request includes changes to the .github/workflows/validate-formatting.yaml file to improve the handling of formatting validation results. The most important changes include updating how the diff variable is referenced and modifying the formatting of the comment body.

Improvements to formatting validation:

Please remove unneeded lines!

🛠️ Type of Change

Please check the relevant options:

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (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 steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)
  • Documentation updated (I have updated any relevant documentation)

📋 Additional Information (optional)

https://github.com/se-bastiaan/ProxmoxVE/pull/4

🔄 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/1285 **Author:** [@se-bastiaan](https://github.com/se-bastiaan) **Created:** 1/6/2025 **Status:** ✅ Merged **Merged:** 1/6/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `fix/formatting-pipeline` --- ### 📝 Commits (2) - [`90ec5d0`](https://github.com/community-scripts/ProxmoxVE/commit/90ec5d0868f44f772d42515032477a71074b702c) fix buffer from base64 - [`2794d58`](https://github.com/community-scripts/ProxmoxVE/commit/2794d58613233bc5d7abeb934bfd924214aa27f0) fix diff ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/validate-formatting.yaml` (+2 -2) </details> ### 📄 Description > **🛠️ Note:** > We are meticulous about merging code into the main branch, so please understand that pull requests not meeting the project's standards may be rejected. It's never personal! > 🎮 **Note for game-related scripts:** These have a lower likelihood of being merged. --- ## ✍️ Description This pull request includes changes to the `.github/workflows/validate-formatting.yaml` file to improve the handling of formatting validation results. The most important changes include updating how the `diff` variable is referenced and modifying the formatting of the comment body. Improvements to formatting validation: * [`.github/workflows/validate-formatting.yaml`](diffhunk://#diff-28c4629b579fe28dcecb337c1687cfe6c5759251be0d297fc2115061e12be0f1L67-R67): Changed the `diff` variable reference from a string concatenation to a direct reference to ensure proper handling of the `steps.shfmt.outputs.diff` output. * [`.github/workflows/validate-formatting.yaml`](diffhunk://#diff-28c4629b579fe28dcecb337c1687cfe6c5759251be0d297fc2115061e12be0f1L78-R78): Updated the comment body construction to use template literals for better readability and maintainability. - - - **_Please remove unneeded lines!_** - Related Issue: # (issue number, if applicable) - Related PR: #1239 - Related Discussion: []()(if applicable) --- ## 🛠️ Type of Change Please check the relevant options: - [ ] Bug fix (non-breaking change that resolves an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (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 steps must be completed for the pull request to be considered: - [ ] Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.) - [ ] Testing performed (I have thoroughly tested my changes and verified expected functionality.) - [ ] Documentation updated (I have updated any relevant documentation) --- ## 📋 Additional Information (optional) https://github.com/se-bastiaan/ProxmoxVE/pull/4 --- <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:22:28 +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#2967
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?