SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-22 13:53:40 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #2319] [MERGED] [gh] Workflow to change date on new json files #3580

New Issue
Closed
opened 2025-11-20 06:05:38 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 06:05:38 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/2319
Author: @michelroegl-brunner
Created: 2/12/2025
Status: ✅ Merged
Merged: 2/13/2025
Merged by: @michelroegl-brunner

Base: main ← Head: workflow_json

📝 Commits (1)

  • 172763b [gh] Workflow to change date on new json files

📊 Changes

2 files changed (+159 additions, -0 deletions)

View changed files

➕ .github/workflows/delete-json-branch.yml (+28 -0)
➕ .github/workflows/update-json-date.yml (+131 -0)

📄 Description

✍️ Description

This Workflow changes the date_create field in newly added .json files and opens a PR for them.
When the JSON Update PR is run, another PR runs to delete the created branch. The random branch name is nesecary as you can not easily push to a existing branch with gh actions. You would have to pull the branch and rebase it, but this dose not seem to work properly.

🔗 Related PR / Discussion / Issue

✅ Prerequisites

Before this PR can be reviewed, the following must be completed:

  • Self-review performed – Code follows established patterns and conventions.
  • Testing performed – Changes have been thoroughly tested and verified.

🛠️ Type of Change

Select all that apply:

  • [] 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • [] 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • [] 🆕 New script – A fully functional and tested script or script set.

📋 Additional Information (optional)

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/2319 **Author:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Created:** 2/12/2025 **Status:** ✅ Merged **Merged:** 2/13/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `workflow_json` --- ### 📝 Commits (1) - [`172763b`](https://github.com/community-scripts/ProxmoxVE/commit/172763bb27bd0229122503027185eafde3cb4d9c) [gh] Workflow to change date on new json files ### 📊 Changes **2 files changed** (+159 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/delete-json-branch.yml` (+28 -0) ➕ `.github/workflows/update-json-date.yml` (+131 -0) </details> ### 📄 Description ## ✍️ Description <!-- Provide a clear and concise description of your changes. --> This Workflow changes the `date_create` field in newly added .json files and opens a PR for them. When the JSON Update PR is run, another PR runs to delete the created branch. The random branch name is nesecary as you can not easily push to a existing branch with gh actions. You would have to pull the branch and rebase it, but this dose not seem to work properly. ## 🔗 Related PR / Discussion / Issue ## ✅ Prerequisites Before this PR can be reviewed, the following must be completed: - [X] **Self-review performed** – Code follows established patterns and conventions. - [X] **Testing performed** – Changes have been thoroughly tested and verified. ## 🛠️ Type of Change Select all that apply: - [] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [X] ✨ **New feature** – Adds new, non-breaking functionality. - [] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [] 🆕 **New script** – A fully functional and tested script or script set. ## 📋 Additional Information (optional) <!-- Provide extra context, screenshots, or references if needed. --> ![image](https://github.com/user-attachments/assets/63fc360e-4b94-4b2f-b7f9-07a0420716e8) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 06:05:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#3580
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?