CI: Make release-related GitHub Actions fork-friendly #1888

Description

This issue is about making some of the GitHub Actions workflows more friendly to contributors who work from forks.

As a non-maintainer, I maintain my own fork of commitizen and periodically sync it with the upstream repository. When I use the Sync fork feature on GitHub, several release/deploy related workflows are triggered on my fork and then fail, for example:

• Bump version
• Publish documentation
• Upload Python Package
• Publish to Homebrew

These failures are expected on a fork, because they require secrets and permissions that only the upstream repository has.
They might only run on the official commitizen-tools/commitizen repository.

Proposal

Add a repository guard to the release/deploy related jobs so that they only run on the upstream repository, for example:

if: github.repository == 'commitizen-tools/commitizen'

Reference

• Official Example: Only run job for a specific repository
• Same question on Stack Overflow

Steps to reproduce

Sync my fork of commitizen with commitizen-tools/commitizen using the GitHub Sync fork feature.

Current behavior

Several release/deploy related workflows are triggered on my fork and then fail.

Desired behavior

They might only run on the official commitizen-tools/commitizen repository.

Screenshots

Environment

Commitizen Version: 4.13.9
Python Version: 3.14.3 (main, Feb 3 2026, 15:32:20) [Clang 15.0.0 (clang-1500.1.0.2.5)]
Operating System: Darwin