Skip to content

Commit

Permalink
Make sure automated commits from other workflows will trigger a rebuild
Browse files Browse the repository at this point in the history
  • Loading branch information
Alexander01998 committed Jan 4, 2025
1 parent b661df2 commit 4ba1101
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 0 deletions.
8 changes: 8 additions & 0 deletions .github/workflows/add_wurst_port.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ on:
permissions:
# To push the automated commit.
contents: write
# To trigger the Jekyll workflow.
actions: write

jobs:

Expand Down Expand Up @@ -54,6 +56,12 @@ jobs:
git add .
git commit -m "[Wurst-Bot] Port Wurst ${{ github.event.inputs.wurst_version }} to Minecraft ${{ github.event.inputs.mc_version }}"
git push
# For some reason the commit above doesn't automatically trigger the
# Jekyll workflow, so we need to explicitly start it here.
- name: Trigger Jekyll workflow
env:
GH_TOKEN: ${{ github.token }}
run: gh workflow run jekyll.yml

announce:
runs-on: ubuntu-latest
Expand Down
9 changes: 9 additions & 0 deletions .github/workflows/announce_wurst_update.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ on:
permissions:
# To push the automated commit.
contents: write
# To trigger the Jekyll workflow.
actions: write

jobs:
announce:
Expand Down Expand Up @@ -50,3 +52,10 @@ jobs:
git add .
git commit -m "[Wurst-Bot] Link Wurst ${{ github.event.inputs.wurst_version }} post to WF thread ${{ steps.announce.outputs.discussion_id }}"
git push
# For some reason the commit above doesn't automatically trigger the
# Jekyll workflow, so we need to explicitly start it here.
- name: Trigger Jekyll workflow
env:
GH_TOKEN: ${{ github.token }}
run: gh workflow run jekyll.yml

0 comments on commit 4ba1101

Please sign in to comment.