Publish workflow: Stricter condition for project forks

[fdcastel]

Forks of this repository that activate workflows might end up building Docker images on a scheduled basis.

• Current:

      if: ${{ github.event_name != 'schedule' || github.repository == 'FirebirdSQL/firebird-docker' }}

• Proposed:

      if: ${{ github.repository == 'FirebirdSQL/firebird-docker' }}

[asfernandes]

I agree we should not try to publish artifacts to docker hub when running in forks, but I don't agree we should disable build and test when committed to main in forks.

You said privately that you have billed and discounted, but how and why?

If your fork is public, then github actions time is free for this project AFAIK. It's why it runs in this FirebirdSQL org, which has nothing different than another org or user.

I leave my fork of FirebirdSQL/firebird public for this and do test things there, running the lots of runners firebird have.

If you want a private fork or do not want the runners, just disable them in your fork.

So I think this job need to be refactored in two jobs, with the publish always disabled in forks.

[fdcastel]

All good points!

I don't agree we should disable build and test when committed to main in forks.

Wasn't my intention. I was just concerned about the publishing aspects.

You said privately that you have billed and discounted, but how and why?

That was a different case, not related to this project.

I often begin my work in private personal forks. In that situation, I had cloned a template repository that already had workflows enabled, which caught me by surprise when I noticed the billing.

But that peculiar scenario became even more unusual when I found out that GitHub automatically disables workflows for forks. I'm starting to suspect that using the 'Use this as a template' feature might bypass this behavior.

So I think this job need to be refactored in two jobs, with the publish always disabled in forks.

Agreed. I’ll proceed the work in this direction. 👍🏻

Thanks, as always, for the valuable insights. I really appreciate it.

[fdcastel]

P.S.: Let's continue this on #30

[fdcastel]

Fixed on #30.