Fix php-cs-fixer push trigger on 3.6 (keep pull_request_target behaviour unchanged)

[berfinyuksel]

Summary

Fix PHP-CS-Fixer silently discarding its own fixes on push to this maintenance branch, without changing any trigger.

-            head_ref: ${{ github.event.pull_request.head.ref }}
-            repository: ${{ github.event.pull_request.head.repo.full_name }}
+            head_ref: ${{ github.head_ref || github.ref_name }}
+            repository: ${{ github.event.pull_request.head.repo.full_name || github.repository }}

The bug

On a push event github.event.pull_request does not exist, so both inputs resolve to empty strings. The reusable workflow then falls back to ref: github.sha — a bare commit, which always lands in detached HEAD. php-cs-fixer runs and computes real fixes, but git-auto-commit-action cannot push from detached HEAD (fatal: You are not currently on a branch), so every fix is silently thrown away.

Same root cause as pimcore/data-quality-management-bundle#328; tracked in pimcore/service-operations#1071.

Why this shape, and not #328's exact change

#328 used repository: ${{ github.repository }}, which is correct for push-only workflows. This branch also has a pull_request_target trigger, so hardcoding the base repo would make every fork PR check out a branch name that doesn't exist in the base repo — trading a silent push failure for a loud fork-PR failure.

The || fallback keeps both paths correct, and matches the idiom already used elsewhere:

Event	head_ref	repository
push	github.ref_name (a branch → not detached)	base repo
PR, same-repo	github.head_ref	base repo
PR, from fork	github.head_ref	fork repo

Fork-PR behaviour is unchanged. On pull_request_target, github.head_ref is exactly github.event.pull_request.head.ref, and the || still resolves to the fork's full_name — so both inputs evaluate to the same values they do today. Only the push path changes.

Triggers are deliberately left untouched: the pull_request vs pull_request_target decision is still open in pimcore/product-management#1311, and this fix intentionally does not pre-empt it.

Verification

• YAML parses; both pull_request_target and push triggers intact; config_file untouched.
• Post-merge, a push run's git-auto-commit step should no longer report detached HEAD.

Related: pimcore/service-operations#1071, pimcore/data-quality-management-bundle#328, pimcore/product-management#1311

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Fixes PHP-CS-Fixer pushes by checking out the branch rather than a detached commit.

Changes:

• Uses push-event fallbacks for branch and repository.
• Preserves existing pull-request and fork behavior.

---

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