jay
/
pi-superpowers-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: jay:4eab93f678aa09aa7fa3a74fdfd0eb397e5a0114
Branches Tags
jay:main
..
compare: jay:48320cb21e8b80d3d3603da9e0dc43af38be8199
Branches Tags
jay:main

No commits in common. "4eab93f678aa09aa7fa3a74fdfd0eb397e5a0114" and "48320cb21e8b80d3d3603da9e0dc43af38be8199" have entirely different histories.
4eab93f678 ... 48320cb21e

1 changed files with 4 additions and 3 deletions
Show Stats Expand all files Collapse all files

7
.gitea/workflows/sync-upstream.yml → .forgejo/workflows/sync-upstream.yml
View File

@ -10,10 +10,11 @@ jobs:
sync: sync:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Checkout from Gitea - name: Checkout from Forgejo
uses: actions/checkout@v4 uses: actions/checkout@v4
with: with:
fetch-depth: 0 fetch-depth: 0
# Forgejo Actions auto-provides GITEA_TOKEN for the current repo
token: ${{ secrets.GITEA_TOKEN }} token: ${{ secrets.GITEA_TOKEN }}
- name: Add upstream remote - name: Add upstream remote
@ -54,8 +55,8 @@ jobs:
- name: Commit and push - name: Commit and push
if: steps.sync.outputs.changed == 'true' if: steps.sync.outputs.changed == 'true'
run: | run: |
git config user.name "gitea-actions[bot]" git config user.name "forgejo-actions[bot]"
git config user.email "gitea-actions@git.vpsj.de" git config user.email "forgejo-actions@git.vpsj.de"
UPSTREAM_SHA=$(git rev-parse --short upstream/main) UPSTREAM_SHA=$(git rev-parse --short upstream/main)
git commit -m "Sync skills from obra/superpowers upstream (${UPSTREAM_SHA})" git commit -m "Sync skills from obra/superpowers upstream (${UPSTREAM_SHA})"