Earl Warren
5acda1e0b2
- add a checklist to the release instructions - use a pattern for push instead of an explicit list of branches it was previously advisable to avoid conflicts when there was no automated backports but it is no longer necessary
26 lines
686 B
YAML
26 lines
686 B
YAML
name: push
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- 'next'
|
|
- 'v*'
|
|
|
|
jobs:
|
|
publish:
|
|
runs-on: docker
|
|
steps:
|
|
- name: update the website submodules
|
|
if: ${{ secrets.WEBSITETOKEN != '' }}
|
|
run: |
|
|
git clone --recursive https://forgejo-website:${{ secrets.WEBSITETOKEN }}@codeberg.org/forgejo/website
|
|
cd website
|
|
git submodule update --remote
|
|
git config user.email "ci@forgejo.org" ; git config user.name "forgejo-website"
|
|
git add .
|
|
if git diff-index --quiet HEAD ; then
|
|
echo Nothing changed, not pushing
|
|
else
|
|
git commit -m 'publish' -a
|
|
git push
|
|
fi
|