Update the C-like style check to an ARM-compatible clang-format version
@ann0see is already working on this.
Since Sep 15, 2026.
Assessment
This issue has not been assessed yet.
Description
Summary
Update the C-like coding-style check to use a newer clang-format version on the Ubuntu 24.04 ARM runner.
The current workflow configures DoozyX/clang-format-lint-action with clangFormatVersion: 14. Version 14 was selected for Ubuntu 22.04 LTS. The job now uses ubuntu-24.04-arm.
Rationale
The Docker action copies bundled clang-format executables into its image. The ARM runner cannot rely on a bundled executable unless that executable supports ARM64.
Ubuntu 24.04 provides an ARM64-native clang-format-18 package. This is a newer supported version and is an ARM-compatible path for the workflow.
Affected area
.github/workflows/coding-style-check.ymlcheck-c-like-stylejob
Required changes
Replace or adapt the formatter invocation so that the ARM job installs and uses the Ubuntu 24.04 ARM64 clang-format-18 package. Do not depend on an architecture-specific formatter binary from the current action unless ARM64 support is verified.
Review and apply any formatting changes that version 18 requires.
Acceptance criteria
- The C-like style job runs successfully on
ubuntu-24.04-arm. - The job uses
clang-formatversion 18 or another explicitly verified newer ARM64-compatible version. - The job checks
.cpp,.h, and.mmfiles with the existing repository style configuration. - Required formatting updates are included or tracked before the version change is enabled.
Research
Ubuntu's package index lists clang-format-18 for Ubuntu 24.04 (noble) on arm64.
- https://packages.ubuntu.com/clang-format
- https://launchpad.net/ubuntu/noble/arm64/clang-format/1:18.0-59~exp2
Backlinks
- Requested by @ann0see in https://github.com/jamulussoftware/jamulus/pull/3954#issuecomment-5679589906
- Related PR: https://github.com/jamulussoftware/jamulus/pull/3954
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 248
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jamulussoftware/jamulus
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jamulussoftware/jamulus#3953 · 2 comments ·
-
AI bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jamulussoftware/jamulus#3901 · 4 comments · 1 reaction ·
-
AI
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jamulussoftware/jamulus#3846 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
jamulussoftware/jamulus#3958 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
jamulussoftware/jamulus#3951 · 1 reaction ·
All issues in jamulussoftware/jamulus
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·