Skip to content

GitHub Actions: switch utility workflows to ubuntu-slim image#2053

Merged
Xottab-DUTY merged 2 commits intodevfrom
Xottab-DUTY-patch-1
Feb 19, 2026
Merged

GitHub Actions: switch utility workflows to ubuntu-slim image#2053
Xottab-DUTY merged 2 commits intodevfrom
Xottab-DUTY-patch-1

Conversation

@Xottab-DUTY
Copy link
Member

I think ubuntu-slim should be slightly faster to start up because they are lightweight containers.
Another thing is unified file system, which could possibly be used to our advantage.

Single-CPU GitHub-hosted runners are available in both public and private repositories. These runners — specified using the workflow label ubuntu-slim — offer a lower-cost option for running lightweight operations. This type of runner is optimized for automation tasks, issue operations and short-running jobs. They are not suitable for typical heavyweight CI/CD builds.
ubuntu-slim runners execute Actions workflows in Ubuntu Linux, inside a container rather than a full VM instance. When the job begins, GitHub automatically provisions a new container for that job. All steps in the job execute in the container, allowing the steps in that job to share information using the runner's file system. When the job has finished, the container is automatically decommissioned. Each container provides hypervisor level 2 isolation.1

Footnotes

  1. https://docs.github.com/en/actions/reference/runners/github-hosted-runners#single-cpu-runners

Xottab-DUTY and others added 2 commits February 19, 2026 16:04
This also switches the workflow to another mirroring action (https://github.com/marketplace/actions/mirror-to) because previous doesn't work with ubuntu-slim currently.
@Xottab-DUTY Xottab-DUTY merged commit 810c134 into dev Feb 19, 2026
10 of 114 checks passed
@github-project-automation github-project-automation bot moved this to Done in Roadmap Feb 19, 2026
@Xottab-DUTY Xottab-DUTY deleted the Xottab-DUTY-patch-1 branch February 19, 2026 16:14
@Xottab-DUTY Xottab-DUTY removed this from Roadmap Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant