Skip push package to GitHub Container Registry

[CarrotManMatt]

In the GitHub workflow to check that the container build correctly, the docker build-push action is used. The push flag should be set to false if the PR is being made from a repository forked from the main project. Pushing will always fail because forked repositories do not have access to push to the GHCR.

Although this will be a limitation on the efficacy of the check/test, there is no full solution. The build check will still occur and any issues with pushing to the GHCR will present themselves after the PR is merged.

[MattyTheHacker]

any issues with pushing to the GHCR will present themselves after the PR is merged. - the ultimate test in prod

[MattyTheHacker]

Rather than skipping - in theory could you write an action that takes the PR, copies it to a local branch and then does the push and dev deploy?

[CarrotManMatt]

That sounds absolutely horrendous. I'd also rather not pull unverified code from someones fork inside the project where it is then privileged to run actions without manual approval. A good GitHub feature that i like is that fork PRs need approval to run checks