Do not run docker build on fork

[FileGo]

Fixes #401.

[codecov]

Codecov Report

Merging #402 (524b4a8) into development (02e1aa5) will decrease coverage by 0.15%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #402      +/-   ##
===============================================
- Coverage        94.10%   93.95%   -0.16%     
===============================================
  Files               32       32              
  Lines             2546     2546              
===============================================
- Hits              2396     2392       -4     
- Misses             112      115       +3     
- Partials            38       39       +1     

Impacted Files	Coverage Δ
resolver/caching_resolver.go	95.27% <0.00%> (-3.15%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 02e1aa5...524b4a8. Read the comment docs.

[0xERR0R]

Do we have the same problem with "Upload results to codecov" step?

[FileGo]

Do we have the same problem with "Upload results to codecov" step?

It works fine, but not sure if that's the desired behaviour? Is there any benefit in codecov upload running on forks?

[0xERR0R]

I was just wondering, why this PR has changed the code coverage. I think, this step can run on forks, but codecov should not consider any results from fork build. Not sure, how it currently works 🤷

[FileGo]

Yeah, not sure either really, it's only one line in a GH yaml 😐