[PR #30] [CLOSED] Rgov rzg/build cache #264

New issue

Closed

opened 2026-03-04 01:35:59 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:35:59 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/spr-networks/super/pull/30
Author: @lts-rad
Created: 5/25/2022
Status: ❌ Closed

Base: main ← Head: rgov-rzg/build-cache

📝 Commits (4)

6afe5cd Use GitHub cache to store build layers
a9483c7 Merge branch 'rzg/build-cache' of https://github.com/rgov/super into rgov-rzg/build-cache
146049f [build] set target
2e2881c Update docker-image.yml

📊 Changes

2 files changed (+35 additions, -8 deletions)

View changed files

📝 .github/workflows/docker-image.yml (+24 -5)
📝 build_docker_compose.sh (+11 -3)

📄 Description

thanks @rgov

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/spr-networks/super/pull/30 **Author:** [@lts-rad](https://github.com/lts-rad) **Created:** 5/25/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `rgov-rzg/build-cache` --- ### 📝 Commits (4) - [`6afe5cd`](https://github.com/spr-networks/super/commit/6afe5cddb6b1ff08b59c2aa71d131ea54b53c599) Use GitHub cache to store build layers - [`a9483c7`](https://github.com/spr-networks/super/commit/a9483c70e0044be8a1444a546d5056b44773bb3a) Merge branch 'rzg/build-cache' of https://github.com/rgov/super into rgov-rzg/build-cache - [`146049f`](https://github.com/spr-networks/super/commit/146049fc5bb00797cb4912c89dce54124cc59586) [build] set target - [`2e2881c`](https://github.com/spr-networks/super/commit/2e2881ca29e5c046518eec33615d9caa26f3feed) Update docker-image.yml ### 📊 Changes **2 files changed** (+35 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker-image.yml` (+24 -5) 📝 `build_docker_compose.sh` (+11 -3) </details> ### 📄 Description thanks @rgov --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>