Skip to content

Add condition to skip pushed tags from forks#9924

Merged
browniebroke merged 1 commit intoencode:mainfrom
browniebroke:fix/release-from-forks
Mar 24, 2026
Merged

Add condition to skip pushed tags from forks#9924
browniebroke merged 1 commit intoencode:mainfrom
browniebroke:fix/release-from-forks

Conversation

@browniebroke
Copy link
Member

Description

After releasing 3.17, when I synced my fork from the command line and pushed the new tag, the release workflow ran (and failed).

Adding a condition to skip running it from forks.

@browniebroke browniebroke requested a review from Copilot March 24, 2026 14:35
@browniebroke browniebroke merged commit 8e99b53 into encode:main Mar 24, 2026
9 checks passed
@browniebroke browniebroke deleted the fix/release-from-forks branch March 24, 2026 14:36
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Prevents the release publishing workflow from running when a release tag is pushed from a fork (e.g., after syncing a fork and pushing tags), avoiding failed/unauthorized release attempts outside the upstream repository.

Changes:

  • Add a job-level condition to run the release build job only in encode/django-rest-framework.
  • Implicitly skip downstream publish/sign/release jobs because they depend on the guarded build job.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants