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

Changelog Action fails on Fork #85

New Issue
Closed
opened 2025-11-20 04:43:29 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 04:43:29 -05:00
Owner
Copy Link

Originally created by @newzealandpaul on GitHub (Nov 19, 2024).

Originally assigned to: @havardthom on GitHub.

What type of issue is this?

Optimisation

A clear and concise description of the issue.

It would be nice if the changelog action did not run, or ran successfully, when triggered on a fork. It fails, and then I get an email about the failure.

Please provide detailed steps to reproduce the issue.

Fork, commit to fork, trigger actions.

Originally created by @newzealandpaul on GitHub (Nov 19, 2024). Originally assigned to: @havardthom on GitHub. ### What type of issue is this? Optimisation ### A clear and concise description of the issue. It would be nice if the changelog action did not run, or ran successfully, when triggered on a fork. It fails, and then I get an email about the failure. ### Please provide detailed steps to reproduce the issue. Fork, commit to fork, trigger actions.
saavagebueno added the not a script issuebug labels 2025-11-20 04:43:29 -05:00
saavagebueno commented 2025-11-20 04:43:30 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 20, 2024):

Can you show what the error is?
I don't think the action can know if it's on a fork or not, you can try this https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow

@havardthom commented on GitHub (Nov 20, 2024): Can you show what the error is? I don't think the action can know if it's on a fork or not, you can try this https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/disabling-and-enabling-a-workflow
saavagebueno commented 2025-11-20 04:43:30 -05:00
Author
Owner
Copy Link

@newzealandpaul commented on GitHub (Nov 20, 2024):

Ah! It was because I didn't have the correct issue label setup. 🤦‍♂️ But thanks for the that tip, I didn't know I could disable a single workflow. This solves the issue, thank you @havardthom

@newzealandpaul commented on GitHub (Nov 20, 2024): Ah! It was because I didn't have the correct issue label setup. 🤦‍♂️ But thanks for the that tip, I didn't know I could disable a single workflow. This solves the issue, thank you @havardthom
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 bug not a script issue
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#85
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?