forked from signalapp/Signal-Android
-
-
Notifications
You must be signed in to change notification settings - Fork 0
62 lines (55 loc) · 2.11 KB
/
update_fork.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
name: Update Fork
on:
workflow_dispatch:
schedule:
- cron: "30 5 * * MON,WED,FRI" # runs every monday, wednesday and friday at 05:30 UTC
permissions:
contents: write
actions: write
jobs:
update_fork:
runs-on: ubuntu-latest
steps:
- name: Checkout Forked Repo
uses: actions/checkout@v4
with:
repository: pixincreate/Signal
ref: main
fetch-depth: "0"
submodules: true
- name: Setup Git
run: git config --global user.email ${{ secrets.EMAIL }} && git config --global user.name pixincreate
- name: Fetch from Upstream
run: |
git remote add upstream https://github.com/signalapp/Signal-Android.git
git fetch upstream --tags
upstream_commit="$(git rev-parse upstream/main)"
echo "Upstream latest commit: ${upstream_commit}"
for forked_commit in $(git rev-list -n 20 main); do
if [ $upstream_commit != $forked_commit ]; then
has_new_commits=true
continue
else
has_new_commits=false
break
fi
done
if [ $has_new_commits == "true" ]; then
git checkout main
git rebase upstream/main || git diff
git submodule update --init --recursive # Update the submodule
git push -f origin main
echo "Rebase successful!"
else
echo "ERROR: No commits to be synced!"
exit 1
fi
build_app:
needs: update_fork
uses: ./.github/workflows/android_build.yml
secrets: inherit
# References:
# https://stackoverflow.com/questions/75192546/is-it-possible-to-call-another-workflow-file-from-another-workflow-files-condit/75225285#75225285
# https://stackoverflow.com/questions/75191443/how-to-check-if-upstreams-head-latest-commit-is-present-in-forked-repo
# https://stackoverflow.com/questions/75191328/why-does-git-rebase-upstream-main-behaves-differently-when-used-github-actions
# https://stackoverflow.com/questions/62750603/github-actions-trigger-another-action-after-one-action-is-completed