zach/z-bar-qt
1
1
Fork 0
Code Issues 23 Pull Requests 3 Actions Packages Projects 1 Releases Wiki Activity

WIP: Feat/task runner ci #162

Draft
AramJonghu wants to merge 14 commits from feat/task-runner-ci into main
pull from: feat/task-runner-ci
merge into: :main
Conversation 2 Commits 14 Files Changed 11
+192 -194
AramJonghu commented 2026-10-23 03:42:44 +02:00
Collaborator
Copy Link
Copy Source

What & why

What

The changes include:

  • Combine CI where it makes sense. This reduces stress on the runner while keeping the logic intact. This could get more improvements with more efficient container choices, adding test runs on Rust and C++, among other minor improvements.
  • ci/Dockerfile got dependency update, image build succeeds.
  • Makefile added with, as of now, basic task runners. More to come in this PR.

Why

Issue #161 illustrates the advantages for task-runners.
The CI steps caused the runner to draw too many resources, crashing the server. While reducing the amount of tasks that can run concurrently does improve things, another layer is good to perhaps get some headroom.

WIP

Docs and branch protection rules can get updated once PR is out of draft. Draft is required to run some runners.

Related issue

#161

Type

CI / build / tooling

Tested

  • Build succeeds
  • Existing tests pass
  • Manually verified

Breaking changes?

No response

Checklist

  • CI passes (format, lint, typecheck)
  • Clean commits
  • No new warnings
  • Docs updated if needed
### What & why ## What The changes include: - Combine CI where it makes sense. This reduces stress on the runner while keeping the logic intact. This could get more improvements with more efficient container choices, adding test runs on Rust and C++, among other minor improvements. - `ci/Dockerfile` got dependency update, image build succeeds. - Makefile added with, as of now, basic task runners. More to come in this PR. ## Why Issue #161 illustrates the advantages for task-runners. The CI steps caused the runner to draw too many resources, crashing the server. While reducing the amount of tasks that can run concurrently does improve things, another layer is good to perhaps get some headroom. ## WIP Docs and branch protection rules can get updated once PR is out of draft. Draft is required to run some runners. ### Related issue #161 ### Type CI / build / tooling ### Tested - [ ] Build succeeds - [ ] Existing tests pass - [ ] Manually verified ### Breaking changes? _No response_ ### Checklist - [ ] CI passes (format, lint, typecheck) - [x] Clean commits - [ ] No new warnings - [ ] Docs updated if needed
AramJonghu added the bugdocumentationenhancement labels 2026-10-23 03:42:57 +02:00
AramJonghu force-pushed feat/task-runner-ci from 5ee4f370d9 to 4ed95c9475 2026-10-23 03:48:21 +02:00 Compare
AramJonghu force-pushed feat/task-runner-ci from 4ed95c9475 to eba5458f15 2026-10-23 04:01:01 +02:00 Compare
AramJonghu force-pushed feat/task-runner-ci from eba5458f15 to 39f99bb336 2026-10-23 04:08:50 +02:00 Compare
AramJonghu force-pushed feat/task-runner-ci from e28f276209 to cc88356099 2026-10-24 00:47:32 +02:00 Compare
AramJonghu force-pushed feat/task-runner-ci from bbdfdfcd8b to b3bd19316b 2026-10-24 00:55:20 +02:00 Compare
AramJonghu commented 2026-10-25 00:27:44 +02:00
Author
Collaborator
Copy Link
Copy Source

@zach I believe rebasing is better than merging from main since it preserves history more linearly. Gitea gives you the option to do so as well. It is what I personally prefer doing.

I'd also advise to not rebase or merge unless you plan to work on the new branch.

@zach I believe rebasing is better than merging from main since it preserves history more linearly. Gitea gives you the option to do so as well. It is what I personally prefer doing. I'd also advise to not rebase or merge unless you plan to work on the new branch.
AramJonghu self-assigned this 2026-10-25 00:27:49 +02:00
zach commented 2026-10-25 00:37:22 +02:00
Owner
Copy Link
Copy Source

Sure, merging is just the first option. I just do it whenever I look through them, but I can stop.

Sure, merging is just the first option. I just do it whenever I look through them, but I can stop.
👍 1
AramJonghu force-pushed feat/task-runner-ci from 65cf06d9d4 to 9bab59ba0f 2026-10-25 01:35:19 +02:00 Compare
AramJonghu added 14 commits 2026-10-25 16:01:53 +01:00
fix(ci): missing dependency wayland-scanner c5dfb306dd
refactor(workflows): combined steps where it makes sense fd938d4e47
ci: rework Dockerfile image + buildx dep added b4f0239e2a
format(clang): make cpp-fmt result a2326dc641
feat(makefile): makefile build & install + progress on cpp and py 9f9d09bc5b
feat(makefile): C++, Python, and Rust checks included (incomplete) cbb108a6dd
feat(makefile): added qmlformat + install -> compile in cpp step a96211a5b5
Merge branch 'main' into feat/task-runner-ci 02fb847268
chore(Dockerfile): add future dependencies 5eb84285a4
fix(clang-tidy): make cpp-lint has proper clang-tidy check 18c474669b
chore(gitignore): nuitka compile files ignored and categorized 0c4e8e805a
chore(gitignore): ordering known files and directories 856c78c380
feat(makefile): added no nuitka option for cpp-compile task 9ad94f1e3e
fix(ci): cpp clang-tidy now properly reads non-build files only
C++ / fmt (pull_request) Successful in 6s
Details
JS/TS / fmt & lint (pull_request) Successful in 16s
Details
Python / fmt & lint (pull_request) Successful in 48s
Details
C++ / build & lint (pull_request) Failing after 2m33s
Details
Python / test & nuitka build (pull_request) Failing after 1m38s
Details
Rust / build, clippy & fmt (pull_request) Failing after 4m41s
Details
b1ef587dd2
AramJonghu force-pushed feat/task-runner-ci from 5adcaa5a0c to b1ef587dd2 2026-10-25 16:01:53 +01:00 Compare
Some checks are pending
C++ / fmt (pull_request) Successful in 6s
Details
JS/TS / fmt & lint (pull_request) Successful in 16s
Details
Python / fmt & lint (pull_request) Successful in 48s
Details
C++ / build & lint (pull_request) Failing after 2m33s
Details
Python / test & nuitka build (pull_request) Failing after 1m38s
Details
Rust / build, clippy & fmt (pull_request) Failing after 4m41s
Details
C++ / build (pull_request)
Required
Python / verify (pull_request)
Required
Rust / build (pull_request)
Required
Some required checks are missing.
This pull request doesn't have enough required approvals yet. 0 of 1 official approvals granted.
You are not authorized to merge this pull request.
This branch is out-of-date with the base branch
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/task-runner-ci:feat/task-runner-ci
git checkout feat/task-runner-ci
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No labels bug documentation enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
AramJonghu Inorishio zach
No Assignees AramJonghu
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: zach/z-bar-qt#162