Skip to content

Commit 619257d

Browse files
committed
2 parents 5b78a00 + 03771bf commit 619257d

3 files changed

Lines changed: 192 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 🐞 General script bug (not Incus-specific)
4+
url: https://github.com/community-scripts/ProxmoxVE/issues/new?template=bug_report.yml
5+
about: >-
6+
This repo only mirrors the scripts. If a script misbehaves in the same way
7+
it would on Proxmox (logic, install steps, app config), report it in the
8+
upstream community-scripts/ProxmoxVE repository so the fix reaches everyone.
9+
- name: 🌟 New script request
10+
url: https://github.com/community-scripts/ProxmoxVE/discussions/new?category=request-script
11+
about: For feature/script requests, please use the ProxmoxVE Discussions section.
12+
- name: 🤔 Questions and Help
13+
url: https://github.com/community-scripts/ProxmoxVE/discussions
14+
about: For suggestions or questions, please use the ProxmoxVE Discussions section.
15+
- name: 💻 Discord
16+
url: https://discord.gg/jsYVk5JBxq
17+
about: Join our Discord server to chat with other users in the community.
Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
name: "🐧 Incus-specific Issue Report"
2+
description: Report an issue that only happens on Incus. For general script bugs, use the ProxmoxVE repo (see the other option in the chooser).
3+
labels: ["bug", "incus"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
## ⚠️ **IMPORTANT - READ FIRST**
9+
- 🧭 **Is this really Incus-specific?** These scripts are mirrored 1:1 from [community-scripts/ProxmoxVE](https://github.com/community-scripts/ProxmoxVE). If the script fails the same way it would on Proxmox (install logic, app configuration, upstream package errors), please report it **upstream in ProxmoxVE** instead — fixes there flow back here automatically. Use this template **only** for problems that are unique to running the script under Incus (e.g. Incus container/VM behaviour, `incus` CLI, storage/network, image differences).
10+
- 🔍 **Search first:** Check the [closed issues](https://github.com/community-scripts/incus/issues?q=is%3Aissue+is%3Aclosed) before opening a new one.
11+
- 🔎 If you hit `[ERROR] in line 23: exit code *: while executing command "$@" > /dev/null 2>&1`, rerun the script in verbose mode before submitting.
12+
13+
Thank you for taking the time to report an issue! Please provide as much detail as possible.
14+
15+
- type: input
16+
id: guidelines
17+
attributes:
18+
label: ✅ Have you read and understood the above guidelines?
19+
placeholder: "yes"
20+
validations:
21+
required: true
22+
23+
- type: dropdown
24+
id: incus_specific
25+
attributes:
26+
label: 🧭 Why is this Incus-specific?
27+
description: "If the same failure would occur on Proxmox, please report it upstream in ProxmoxVE instead."
28+
options:
29+
- ""
30+
- "It fails only on Incus and works (or would work) on Proxmox"
31+
- "It relates to the Incus CLI / storage / network / image"
32+
- "I'm not sure (this issue may be moved upstream)"
33+
validations:
34+
required: true
35+
36+
- type: dropdown
37+
id: verbose_run
38+
attributes:
39+
label: 🔎 Did you run the script with verbose mode enabled?
40+
description: "Required for debugging any script issue. A verbose log is mandatory."
41+
options:
42+
- ""
43+
- "Yes, verbose mode was enabled and the output is included below"
44+
- "No (this issue will likely be closed automatically)"
45+
validations:
46+
required: true
47+
48+
- type: input
49+
id: script_name
50+
attributes:
51+
label: 📜 What is the name of the script you are using?
52+
placeholder: "e.g., NextcloudPi, Zigbee2MQTT"
53+
validations:
54+
required: true
55+
56+
- type: input
57+
id: script_command
58+
attributes:
59+
label: 📂 What was the exact command used to execute the script?
60+
placeholder: "e.g., bash -c \"$(curl -fsSL https://raw.githubusercontent.com/community-scripts/incus/main/ct/zigbee2mqtt.sh)\""
61+
validations:
62+
required: true
63+
64+
- type: dropdown
65+
id: instance_type
66+
attributes:
67+
label: 📦 Incus instance type
68+
options:
69+
- ""
70+
- Container
71+
- Virtual Machine
72+
validations:
73+
required: true
74+
75+
- type: checkboxes
76+
validations:
77+
required: true
78+
attributes:
79+
label: ⚙️ What settings are you using?
80+
options:
81+
- label: Default Settings
82+
- label: Advanced Settings
83+
84+
- type: markdown
85+
attributes:
86+
value: "💡 **Tip:** If you are using Advanced Settings, please test with Default Settings before submitting an issue."
87+
88+
- type: dropdown
89+
id: linux_distribution
90+
attributes:
91+
label: 🖥️ Which Linux distribution is the instance running?
92+
options:
93+
-
94+
- Alpine
95+
- Debian 11
96+
- Debian 12
97+
- Debian 13
98+
- Ubuntu 22.04
99+
- Ubuntu 24.04
100+
- Ubuntu 24.10
101+
validations:
102+
required: true
103+
104+
- type: input
105+
id: incus_version
106+
attributes:
107+
label: 📈 Which Incus version are you on?
108+
placeholder: "run `incus --version` on your host"
109+
validations:
110+
required: true
111+
112+
- type: input
113+
id: host_os
114+
attributes:
115+
label: 🧱 Which OS/distribution is the Incus host running?
116+
placeholder: "e.g., Debian 12, Ubuntu 24.04, Arch"
117+
validations:
118+
required: true
119+
120+
- type: textarea
121+
id: issue_description
122+
attributes:
123+
label: 📝 Provide a clear and concise description of the issue.
124+
validations:
125+
required: true
126+
127+
- type: textarea
128+
id: steps_to_reproduce
129+
attributes:
130+
label: 🔄 Steps to reproduce the issue.
131+
placeholder: "e.g., Step 1: ..., Step 2: ..."
132+
validations:
133+
required: true
134+
135+
- type: textarea
136+
id: error_output
137+
attributes:
138+
label: ❌ Paste the full error output (if available).
139+
placeholder: "Include any relevant logs or error messages."
140+
validations:
141+
required: true
142+
143+
- type: textarea
144+
id: additional_context
145+
attributes:
146+
label: 🖼️ Additional context (optional).
147+
placeholder: "Include screenshots, code blocks (use triple backticks ```), or any other relevant information."
148+
validations:
149+
required: false

.github/workflows/sync-scripts.yml

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@ on:
2020
description: "ProxmoxVE ref to sync from"
2121
required: false
2222
default: "main"
23+
# Fired by community-scripts/ProxmoxVE on every ct/ or install/ change so the
24+
# mirror tracks upstream within minutes instead of waiting for the daily cron.
25+
repository_dispatch:
26+
types: [proxmoxve-scripts-changed]
2327

2428
permissions:
2529
contents: write
@@ -130,6 +134,7 @@ jobs:
130134
exit $fail
131135
132136
- name: Open a pull request
137+
id: cpr
133138
uses: peter-evans/create-pull-request@v6
134139
with:
135140
branch: sync/proxmoxve-scripts
@@ -151,6 +156,27 @@ jobs:
151156
overwritten by the next run.
152157
delete-branch: true
153158

159+
# A sync PR only ever mirrors upstream, so it is approved and merged
160+
# automatically. A separate app identity does the approval because a PR
161+
# cannot be approved by the identity that opened it.
162+
- name: Generate token for approve + merge
163+
id: merge-token
164+
if: steps.cpr.outputs.pull-request-number
165+
uses: actions/create-github-app-token@v3
166+
with:
167+
app-id: ${{ secrets.APP_ID_APPROVE_AND_MERGE }}
168+
private-key: ${{ secrets.APP_KEY_APPROVE_AND_MERGE }}
169+
170+
- name: Approve and merge the sync PR
171+
if: steps.cpr.outputs.pull-request-number
172+
env:
173+
GH_TOKEN: ${{ steps.merge-token.outputs.token }}
174+
PR_NUMBER: ${{ steps.cpr.outputs.pull-request-number }}
175+
run: |
176+
set -euo pipefail
177+
gh pr review "$PR_NUMBER" --approve
178+
gh pr merge "$PR_NUMBER" --squash --admin --delete-branch
179+
154180
- name: Ask core to regenerate headers
155181
if: success()
156182
continue-on-error: true

0 commit comments

Comments
 (0)