Skip to content

Archlinux Kernel based on different schedulers and some other performance improvements.

issue_template: Add issue templates for linux-cachyos (#723)

Peter Jungf086532ee69c
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 00000000..cd88acbb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,129 @@
+name: Bug Report
+description: Report a bug or regression in a CachyOS kernel
+title: "[BUG] "
+labels: ["bug"]
+assignees: [ptr1337, sir_lucjan, 1Naim, ventureoo]
+body:
+ - type: checkboxes
+ id: preflight
+ attributes:
+ label: Pre-flight checklist
+ description: Please confirm the following before submitting.
+ options:
+ - label: I have searched existing issues and this is not a duplicate.
+ required: true
+ - label: I have read the [Contributing Guidelines](https://github.com/CachyOS/linux-cachyos/blob/master/CONTRIBUTING.md).
+ required: true
+ - label: I have verified the issue is reproducible with the latest available CachyOS kernel.
+ required: true
+
+ - type: dropdown
+ id: upstream_check
+ attributes:
+ label: Upstream / vanilla kernel check
+ description: Have you tested with an unmodified upstream kernel to determine if this is CachyOS-specific?
+ options:
+ - I tested with a vanilla/upstream kernel and the issue does NOT reproduce there (CachyOS-specific bug)
+ - I tested with a vanilla/upstream kernel and the issue ALSO reproduces there (upstream bug — please report upstream)
+ - I was unable to test with a vanilla/upstream kernel
+ validations:
+ required: true
+
+ - type: dropdown
+ id: kernel_variant
+ attributes:
+ label: Kernel variant
+ description: Which CachyOS kernel package are you using?
+ options:
+ - linux-cachyos (EEVDF, Clang)
+ - linux-cachyos-bore (BORE, GCC)
+ - linux-cachyos-eevdf (EEVDF, GCC)
+ - linux-cachyos-bmq (BMQ, GCC)
+ - linux-cachyos-hardened
+ - linux-cachyos-lts
+ - linux-cachyos-rt-bore
+ - linux-cachyos-server
+ - linux-cachyos-deckify
+ - linux-cachyos-rc
+ - linux-cachyos-gcc (GCC)
+ - Other (specify in description)
+ validations:
+ required: true
+
+ - type: textarea
+ id: bugreport
+ attributes:
+ label: System information (cachyos-bugreport.sh)
+ description: |
+ Please run `cachyos-bugreport.sh` and paste the output here.
+ If you are unable to run the script, provide the information manually below.
+ render: text
+ validations:
+ required: true
+
+ - type: textarea
+ id: manual_sysinfo
+ attributes:
+ label: Manual system information (if cachyos-bugreport.sh is unavailable)
+ description: |
+ If you cannot run `cachyos-bugreport.sh`, please provide manually:
+ - Kernel version (`uname -r`)
+ - CPU model
+ - GPU model & driver (if relevant)
+ - Architecture (x86-64, x86-64-v3, x86-64-v4, znver4)
+ - Active SCX scheduler (if any)
+ render: text
+
+ - type: textarea
+ id: description
+ attributes:
+ label: Bug description
+ description: A clear and concise description of what the bug is.
+ placeholder: Describe the problem…
+ validations:
+ required: true
+
+ - type: textarea
+ id: steps
+ attributes:
+ label: Steps to reproduce
+ description: Minimal steps needed to trigger the issue.
+ placeholder: |
+ 1. …
+ 2. …
+ 3. …
+ validations:
+ required: true
+
+ - type: textarea
+ id: expected
+ attributes:
+ label: Expected behavior
+ description: What did you expect to happen?
+ validations:
+ required: true
+
+ - type: textarea
+ id: actual
+ attributes:
+ label: Actual behavior
+ description: What actually happened?
+ validations:
+ required: true
+
+ - type: textarea
+ id: logs
+ attributes:
+ label: Logs / stack traces
+ description: |
+ Paste relevant kernel logs here (`dmesg`, `journalctl -b`, oops/panic output, etc.).
+ Wrap large outputs in a `<details>` block if needed.
+ render: text
+
+ - type: textarea
+ id: system_info
+ attributes:
+ label: Additional system information
+ description: |
+ Any other relevant info (RAM amount, desktop environment, init system, etc.).
+ Output of `inxi -Fxxxz` or `neofetch` is helpful.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 00000000..6a3a3ac7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+ - name: CachyOS Discord
+ url: https://discord.gg/qJqj94uFwE
+ about: Chat with the community for general questions and support.
+ - name: CachyOS Telegram
+ url: https://t.me/+zCzPX4cAFjk1MTYy
+ about: Join the Telegram group for real-time support.
+ - name: CachyOS Wiki
+ url: https://wiki.cachyos.org/features/kernel
+ about: Read the kernel documentation and FAQ before opening an issue.
+ - name: CachyOS Forum
+ url: https://discuss.cachyos.org
+ about: Ask general usage questions on the forum.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 00000000..036bcc38
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,68 @@
+name: Feature Request / Patch Submission
+description: Suggest a new patch, config change, or feature for a CachyOS kernel variant
+title: "[FEATURE] "
+labels: ["enhancement"]
+assignees: [ptr1337, sir_lucjan, 1Naim, ventureoo]
+body:
+ - type: checkboxes
+ id: preflight
+ attributes:
+ label: Pre-flight checklist
+ options:
+ - label: I have searched existing issues/PRs and this has not been requested before.
+ required: true
+ - label: I have read the [Contributing Guidelines](https://github.com/CachyOS/linux-cachyos/blob/master/CONTRIBUTING.md).
+ required: true
+
+ - type: checkboxes
+ id: request_type
+ attributes:
+ label: Request type
+ description: What kind of change are you requesting? (check all that apply)
+ options:
+ - label: New patch / patchset inclusion
+ - label: Kernel config change (enable/disable option)
+ - label: New kernel variant
+ - label: Scheduler tuning / addition
+ - label: Compiler / LTO / PGO optimization
+ - label: Security hardening
+ - label: Driver or hardware enablement
+ - label: Other
+
+ - type: textarea
+ id: summary
+ attributes:
+ label: Summary
+ description: A concise description of the feature or patch you are requesting.
+ placeholder: What should be added or changed, and why?
+ validations:
+ required: true
+
+ - type: textarea
+ id: motivation
+ attributes:
+ label: Motivation / use case
+ description: Why is this useful? What problem does it solve or what performance/security benefit does it bring?
+ validations:
+ required: true
+
+ - type: textarea
+ id: patch_link
+ attributes:
+ label: Patch / upstream reference (if available)
+ description: |
+ Link to the upstream commit, mailing list thread, GitHub PR, or patch file.
+ If you have a patch ready, you can attach it or open a Pull Request directly.
+ placeholder: "https://lore.kernel.org/… or https://github.com/…"
+
+ - type: textarea
+ id: testing
+ attributes:
+ label: Testing / benchmarks
+ description: Have you tested this patch or config change? Share benchmark results, test logs, or observations.
+
+ - type: textarea
+ id: additional
+ attributes:
+ label: Additional context
+ description: Anything else that might be relevant (dependencies, conflicts with existing patches, etc.).