Since PR #1553, any time I push changes from pokeapi/master to my own fork's master branch, it begins a series of CI actions automatically. While some pass, some of them fail (because I don't have the credentials to log into DockerHub) leading to an email notification each time I sync with upstream.
I believe that the issue was the added branch: master qualifier for the push trigger in the release.yml CI workflow. That being said, since this PR the docker-build-and-push.yml workflow has been automatically started each time as well which is the cause of all the failures. Do we know what made these actions start running on forks?
Steps to Reproduce:
- Create fork of repo
- Push any changes to the
master branch
Since PR #1553, any time I push changes from pokeapi/master to my own fork's master branch, it begins a series of CI actions automatically. While some pass, some of them fail (because I don't have the credentials to log into DockerHub) leading to an email notification each time I sync with upstream.
I believe that the issue was the added
branch: masterqualifier for thepushtrigger in therelease.ymlCI workflow. That being said, since this PR thedocker-build-and-push.ymlworkflow has been automatically started each time as well which is the cause of all the failures. Do we know what made these actions start running on forks?Steps to Reproduce:
masterbranch