[PR #247] [MERGED] Add autolabeler github workflow #2645

Closed
opened 2026-02-26 13:30:53 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/247
Author: @havardthom
Created: 11/14/2024
Status: Merged
Merged: 11/14/2024
Merged by: @MickLesk

Base: mainHead: autolabeler


📝 Commits (1)

  • b00d635 Add autolabeler github workflow

📊 Changes

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

View changed files

.github/autolabeler-config.json (+71 -0)
.github/workflows/autolabeler.yml (+65 -0)

📄 Description

Note

We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description

Add github workflow that auto labels pull requests based on file changes in the PR. It labels based on filestatus and glob rules which can be found in .github/autolabeler-config.json. This does not cover all scenarios but it is a start. Labelling PRs is a prerequisite for adding a github release drafter.

Labels and rules summarized:
breaking change - files removed or renamed in directories"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"
new script - files added in directories "ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"
update script - files modified in directories "ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"
delete script - files removed in directories "ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"
rename script - files renamed in directories "ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"
frontend - any change in directory "frontend/**"
documentation - any change in directory "json/**"
maintenance - any change to "*.md", ".github/**"
high risk - any change to "misc/build.func", "misc/install.func"

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

If there are other pull requests or discussions related to this change, please link them here:

  • Related PR #

🔄 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/247 **Author:** [@havardthom](https://github.com/havardthom) **Created:** 11/14/2024 **Status:** ✅ Merged **Merged:** 11/14/2024 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `autolabeler` --- ### 📝 Commits (1) - [`b00d635`](https://github.com/community-scripts/ProxmoxVE/commit/b00d635c9ea063be729caf16bc589392d3b26683) Add autolabeler github workflow ### 📊 Changes **2 files changed** (+136 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/autolabeler-config.json` (+71 -0) ➕ `.github/workflows/autolabeler.yml` (+65 -0) </details> ### 📄 Description > [!NOTE] > We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged. ## Description Add github workflow that auto labels pull requests based on file changes in the PR. It labels based on filestatus and glob rules which can be found in `.github/autolabeler-config.json`. This does not cover all scenarios but it is a start. Labelling PRs is a prerequisite for adding a github release drafter. Labels and rules summarized: `breaking change` - files removed or renamed in directories`"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"` `new script` - files added in directories `"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"` `update script` - files modified in directories `"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"` `delete script` - files removed in directories `"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"` `rename script` - files renamed in directories `"ct/**", "install/**", "misc/**", "turnkey/**", "vm/**"` `frontend` - any change in directory `"frontend/**"` `documentation` - any change in directory `"json/**"` `maintenance` - any change to `"*.md", ".github/**"` `high risk` - any change to `"misc/build.func", "misc/install.func"` ## Type of change Please check the relevant option(s): - [ ] Bug fix (non-breaking change that resolves an issue) - [x] 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/75f1d146-ce6c-4d6f-951d-ff85636da37c) ## Related Pull Requests / Discussions If there are other pull requests or discussions related to this change, please link them here: - Related PR # --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 13:30:53 +03:00
Sign in to join this conversation.
No milestone
No project
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/ProxmoxVE#2645
No description provided.