Skip to content

Fix keep-alive: re-enable workflow via API instead of pushing to protected master #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danifr merged 1 commit into from
Oct 26, 2026
Merged

Fix keep-alive: re-enable workflow via API instead of pushing to protected master #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 4 additions & 17 deletions .github/workflows/keep-alive.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,8 @@ jobs:
name: Keep workflow alive
runs-on: ubuntu-latest
permissions:
contents: write
actions: write
steps:
- uses: actions/checkout@v6
with:
ref: master

- name: commit IF last commit is older than 50 days
run: |
datethen=$(date -d "-50 days" --utc +%s)
last_push=$(git log -1 --format=%ct)
if [ "$last_push" -le "$datethen" ]; then
git config user.name "Github Actions Keepalive Bot"
git config user.email "<>"
git commit -m "Empty commit to keep the github workflows alive" --allow-empty
git push origin master
else
echo "Last commit is recent enough, skipping keepalive commit."
fi
# Re-enables the scheduled workflow via the GitHub API instead of pushing
# an empty commit to master (which is blocked by the branch ruleset).
- uses: liskin/gh-workflow-keepalive@f72ff1a1336129f29bf0166c0fd0ca6cf1bcb38c # v1
Loading