Skip to content

ci: stop release-please self-triggering loop on its own branch #6105

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
arcjet-rei merged 1 commit into from
Jun 29, 2026
Merged

ci: stop release-please self-triggering loop on its own branch #6105

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
6 changes: 6 additions & 0 deletions .github/workflows/push.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,12 @@ jobs:

release:
runs-on: ubuntu-latest
# Only run Release Please on `main`. It pushes to
# `release-please--branches--main` using a GitHub App token, and App token
# pushes (unlike `GITHUB_TOKEN`) re-trigger workflows — so running this job
# on that branch makes it force-push and re-trigger itself in an infinite
# loop. The `test` and `examples` jobs still run on the release branch.
if: github.ref == 'refs/heads/main'
# Release Please is very fast, so we set a tiny timeout
timeout-minutes: 2
# The GitHub App token handles write permissions for contents and
Expand Down
Loading