Sulkta-Coop/element-x-ada
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ci(upstream-sync): fetch from GitHub directly, skip the mirror layer

Browse source 
The Gitea pull-mirror of element-hq/element-x-android is slow to
populate its initial clone (~12 GB). Rather than block workflow
verification on the mirror landing, fetch straight from GitHub — the
runner has outbound access and GitHub isn't flaky. The mirror stays in
place as a fallback / LAN-cache for humans doing manual git fetches.
This commit is contained in:
Cobb 2026-04-17 11:06:57 -07:00
parent b61ebd2f11
commit d25549fcc9
1 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

13
.gitea/workflows/upstream-sync.yml
View file

@ -27,14 +27,15 @@ jobs:
# Built-in token Gitea hands us — scoped to this repo, has push. # Built-in token Gitea hands us — scoped to this repo, has push.
token: ${{ secrets.GITEA_TOKEN }} token: ${{ secrets.GITEA_TOKEN }}
- name: Wire upstream mirror + fetch wallet - name: Fetch upstream + wallet
run: | run: |
set -euo pipefail set -euo pipefail
# Sulkta-Coop/element-x-upstream is a read-only pull-mirror of # Fetch directly from GitHub. We also have a Gitea pull-mirror
# github.com/element-hq/element-x-android. Kept local for # at Sulkta-Coop/element-x-upstream that tracks this same repo,
# LAN-speed fetches and offline resilience. # but sourcing from GitHub keeps the workflow independent of
git remote add upstream http://192.168.0.5:3001/Sulkta-Coop/element-x-upstream.git # the mirror's health — one less moving part to diagnose.
git fetch upstream develop git remote add upstream https://github.com/element-hq/element-x-android.git
git fetch --depth=500 upstream develop
git fetch origin wallet:refs/remotes/origin/wallet git fetch origin wallet:refs/remotes/origin/wallet
- name: Fast-forward main - name: Fast-forward main