Closed khalyomede closed 2 years ago
https://github.com/bhushan/Stash-View/blob/master/.github/workflows/php-cs-fixer.yml
Check here @khalyomede .. see if extract branch name helps..
Thanks for the link! Actually, I thought about it. What do you think, instead of running php-cs-fixer and commiting in the github action, instead we just check if the pull request passes the lint check?
This would help simplifying the process, with the github action only sticking to validations (maybe in the future it will also run the tests in the same time).
IMHO its not a good idea.. we are humans ... and we cannot run php-cs-fixer every time before we push code.. i have good experience of that.. but TBH its upto you to decide
Description
When a Github user creates a pull request and use its own forked branch as source, the github action step that runs php-cs-fixer fails to find a branch on the destination repository (this one) with the same name as the fork branch name.
See this failure on this pull request for example.
Reproduce the issue
Expected behavior
No failure when the fork branch code is complying with php-cs-fixer configuration and the fork branch does not exist on the source repository.